Having nodes talk to each other.

[Chandrashekhar Mullaparthi]

Check the cookie the nodes are actually using to be really sure.

(abcd@REDACTED)2> erlang:get_cookie().
'KJRLCCCBTWIDUUUIHMWT'
(abcd@REDACTED)3>

Make sure they are both the same. You can run epmd in debug mode. Shutdown
your erlang nodes, kill epmd, and start it up again using 

epmd -debug

Then start your erlang shells and see what is happening. 

cheers
Chandru

-----Original Message-----
From: Louis van der Stam [mailto:Louis.van.der.Stam@REDACTED]
Sent: 20 December 2002 13:13
To: erlang-questions@REDACTED
Subject: Having nodes talk to each other.


Hello,

I have seen messages here concerning the problem I'm having, from the
responses I have read, I conclude my problem is different or is it .....

I'm having difficulty getting two Erlang nodes on the same machine
communicate with each other. net_adm:ping('n1@REDACTED'). fails from n2 and vise
versa. I'm starting the two erlang nodes with '> erl -sname n1' and '> erl
-sname n2' respectively. Before starting I had edited the .erlang.cookie
file in my HOME directory to contain mycookie without quotes. In my
experience this in enough to get two nodes communicating.

The installation where this fails is a Tru64 running R9 (it compiled without
problems). Both nodes create a listen port in the TCP stack, but I never see
a connection being established.

Am I overlooking some simple configuration item or ....?

Is there a switch, ... that instructs erl to write some debuging/traceing
information concerning connections and/or connection attempts and failure
causes?

Regards,

Louis van der Stam



NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.