[erlang-questions] Slave node restart not working

[Adam Lindberg]

I can see that the new beam process for the slave node actually 
dissappears, and it and it is not possible to ping it.

I have verified this behavior on Windows as well.


» ps aux | grep beam | wc -l
1

(
)24> net_adm:ping(
).
pang
(
)25> net_adm:ping(
).
pang
(
)26> slave:start(yama, apa).
{
}
(
)27> net_adm:ping(
).
pong

» ps aux | grep beam | wc -l
2

(
)28> rpc:call(
, init, restart, []).
ok
(
)29> net_adm:ping(
).
pang
(
)30> nodes().
[]

» ps aux | grep beam | wc -l
1


Cheers,
Adam



Andrey Pampukha wrote:
> I've checked, slave doesn't want to work at my machine because of
> absence of ssh-server, but ct_slave works:
>
)1>  ct_slave:start(te).
> {
}
> (
)2>  nodes().
> [
]
> (
)3>  rpc:call(
,init,restart,[]).
> ok
> (
)4>  nodes().
> []
> (
)5>  net_adm:ping(
).
> pong
> (
)6>  nodes().
> [
]
>
>
> 2011/2/4, Andrey Pampukha<
>:
>> Hi,
>>
>> Looks like nobody reconnects the slave node back to the master after
>> restart.
>> Try to ping it, I believe it should work.
>>
>> Andrey.
>>
>> 2011/2/4, Adam Lindberg<
>:
>>> Hi!
>>>
>>> I'm running a slave node in a project, and sometimes we want to restart
>>> the slave node. However, it seems that init:restart() shuts down the
>>> node instead of restarting in.
>>>
>>> The documentation for init:restart() says that it restarts the node in
>>> the current emulator, which makes me wonder why it goes down instead of
>>> restarts. The node should have everything it needs to restart based on
>>> the boot flags etc.
>>>
>>>
>>> (
)5>  slave:start(yama, apa).
>>> {
}
>>> (
)6>  nodes().
>>> [
]
>>> (
)7>  rpc:call('
', init, restart, []).
>>> ok
>>> (
)8>  nodes().
>>> []
>>>
>>> There is no crash dump generated as well. Why doesn't the slave node
>>> restart?
>>>
>>> Cheers,
>>> Adam
>>>
>>>
>>> ________________________________________________________________
>>> erlang-questions (at) erlang.org mailing list.
>>> See http://www.erlang.org/faq.html
>>> To unsubscribe; mailto:
>>>
>>>