Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Erlang Programming
Home
+ new post
About this group
Join this group
erl_call problem
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Andrew Gopienko  
View profile  
 More options Oct 7 2012, 9:53 am
From: Andrew Gopienko <gopie...@gmail.com>
Date: Sun, 7 Oct 2012 20:53:33 +0700
Local: Sun, Oct 7 2012 9:53 am
Subject: [erlang-questions] erl_call problem
Print | Individual message | Show original | Report this message | Find messages by this author

We are using erl_call for nodes monitoring and sometimes erl_call failed
with message 'erl_call: failed to connect to node node...@192.168.1.2'
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...@192.168.1.2, fd=-1, errno=0,
erl_errno=5
--------------------------------------------------------------------------- -------------------

In what cases the node returns 'salive' ?

Andrew Gopienko

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Andrew Gopienko  
View profile  
 More options Oct 8 2012, 3:01 am
From: Andrew Gopienko <gopie...@gmail.com>
Date: Mon, 8 Oct 2012 14:01:07 +0700
Local: Mon, Oct 8 2012 3:01 am
Subject: [erlang-questions] erl_call problem
Print | Individual message | Show original | Report this message | Find messages by this author

We are using erl_call for nodes monitoring and sometimes erl_call failed
with message 'erl_call: failed to connect to node node...@192.168.1.2'
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...@192.168.1.2, fd=-1, errno=0,
erl_errno=5
--------------------------------------------------------------------------- -------------------

In what cases the node returns 'salive' ?

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Serge Aleynikov  
View profile  
 More options Oct 8 2012, 9:07 am
From: Serge Aleynikov <se...@aleynikov.org>
Date: Mon, 08 Oct 2012 09:07:07 -0400
Local: Mon, Oct 8 2012 9:07 am
Subject: Re: [erlang-questions] erl_call problem
Print | Individual message | Show original | Report this message | Find messages by this author
You normally receive 'salive' in the distribution protocol when you try
to connect to a server node from another client node that has a name
already known to the server node.

I.e.:

shell1> erl -sname a

shell2> erl_call -sname a -h b -a 'timer sleep [60000]'
shell3> erl_call -sname a -h b -a 'timer sleep [60000]'

You should get a failed 'salive' connection error in shell3.

Regards,

Serge

On 10/8/2012 3:01 AM, Andrew Gopienko wrote:

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google