[erlang-questions] Unexpected error report from Global name server
Trevor Woollacott [ MTN - Innovation Centre ]
Woolla_T@REDACTED
Thu Oct 25 16:08:09 CEST 2007
Hi
I'm using Erlang R11-B4.
I started 2 runtimes using -connect_all false
and get error reports when I connect the nodes.
Node1:
Erlang (BEAM) emulator version 5.5.4 [async-threads:0]
Eshell V5.5.4 (abort with ^G)
(admin4@REDACTED)1>
=ERROR REPORT==== 24-Oct-2007::15:13:20 ===
The global_name_server received an unexpected message:
handle_info({nodeup,admin3@REDACTED}, _)
Node2:
Erlang (BEAM) emulator version 5.5.4 [async-threads:0]
Eshell V5.5.4 (abort with ^G)
(admin3@REDACTED)1> auth:is_auth( admin4@REDACTED ).
=ERROR REPORT==== 24-Oct-2007::15:13:20 ===
The global_name_server received an unexpected message:
handle_info({nodeup,admin4@REDACTED}, _)
yes
I tested the same on R11-B2, and no error reports are generated.
Is this an intended feature?
Regards
Primanathan Reddy
NOTE: This e-mail message is subject to the MTN Group disclaimer see http://www.mtn.co.za/default.aspx?pid=34411
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20071025/940de12f/attachment.htm>
More information about the erlang-questions
mailing list