[erlang-questions] erl_call problem

[Andrew Gopienko]

We are using erl_call for nodes monitoring and sometimes erl_call failed
with message 'erl_call: failed to connect to node node_01@REDACTED'
Node at this time is alive and works as usually.

We found that node at this time returns status 'salive' instead of expected
'sok'.

----------------------------------------------------------------------------------------------
ei_xconnect: Sun Oct  7 16:45:00 2012: -> CONNECT attempt to connect to
node_01
ei_epmd_r4_port: Sun Oct  7 16:45:00 2012: -> PORT2_REQ alive=node_01
ip=192.168.1.2
ei_epmd_r4_port: Sun Oct  7 16:45:00 2012: <- PORT2_RESP result=0 (ok)
ei_epmd_r4_port: Sun Oct  7 16:45:00 2012:    port=52658 ntype=77 proto=0
dist-high=5 dist-low=5
ei_xconnect: Sun Oct  7 16:45:00 2012: -> CONNECT connected to remote
recv_status: Sun Oct  7 16:45:00 2012: <- len=6
recv_status: Sun Oct  7 16:45:00 2012: <- buf[0]=s (115)
recv_status: Sun Oct  7 16:45:00 2012: <- buf[1]=a (97)
recv_status: Sun Oct  7 16:45:00 2012: <- buf[2]=l (108)
recv_status: Sun Oct  7 16:45:00 2012: <- buf[3]=i (105)
recv_status: Sun Oct  7 16:45:00 2012: <- buf[4]=v (118)
recv_status: Sun Oct  7 16:45:00 2012: <- buf[5]=e (101)
ex_xconnect: Sun Oct  7 16:45:00 2012: RECV_STATUS failed
ei_xconnect: Sun Oct  7 16:45:00 2012: -> CONNECT failed
erl_call: failed to connect to node node_01@REDACTED, fd=-1, errno=0,
erl_errno=5
----------------------------------------------------------------------------------------------

In what cases the node returns 'salive' ?


Andrew Gopienko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20121007/75a6ffde/attachment.htm>