node startup crash

[Serge Aleynikov]

Thanks for the advice, but I tried that a couple of times before 
submitting this posting.  Then I also did:

~/otp_src_R10B-4>killall epmd beam
~/otp_src_R10B-4>rm -fr /usr/local/lib/erlang
~/otp_src_R10B-4>make install
~/otp_src_R10B-4>erl -sname abc
{error_logger,{{2005,4,23},{21,41,36}},'Protocol: ~p: register error: 
~p~n',[inet_tcp,{timeout,{gen_server,call,[erl_epmd,{register,abc,35363},15000]}}]}
{error_logger,{{2005,4,23},{21,41,36}},crash_report,[[{pid,<0.18.0>},{registered_name,net_kernel},{error_info,{error,badarg}
...

The same crash.  There's not a lot of stuff running on this host either. 
  Below is the output of "ps -ax".  We can also see that epmd was 
started from the right distribution (erts-5.4.5).  This is somewhat 
annoying, as  I am not sure what else can be checked in order to 
overcome this crash...

Thank you.

Serge

   PID TTY      STAT   TIME COMMAND
     1 ?        S      0:00 init [3]
     2 ?        SW     0:00 [migration/0]
     3 ?        SWN    0:00 [ksoftirqd/0]
     4 ?        SW     0:00 [migration/1]
     5 ?        SWN    0:00 [ksoftirqd/1]
     6 ?        SW     0:03 [migration/2]
     7 ?        SWN    0:00 [ksoftirqd/2]
     8 ?        SW     0:00 [migration/3]
     9 ?        SWN    0:00 [ksoftirqd/3]
    10 ?        SW<    0:00 [events/0]
    11 ?        SW<    0:00 [events/1]
    12 ?        SW<    0:00 [events/2]
    13 ?        SW<    0:00 [events/3]
    14 ?        SW<    0:00 [khelper]
    15 ?        SW<    0:00 [kblockd/0]
    16 ?        SW<    0:00 [kblockd/1]
    17 ?        SW<    0:00 [kblockd/2]
    18 ?        SW<    0:00 [kblockd/3]
    53 ?        SW     0:00 [kirqd]
    54 ?        SW     0:00 [pdflush]
    55 ?        SW     0:11 [pdflush]
    56 ?        SW     0:00 [kswapd0]
    57 ?        SW<    0:00 [aio/0]
    58 ?        SW<    0:00 [aio/1]
    59 ?        SW<    0:00 [aio/2]
    60 ?        SW<    0:00 [aio/3]
   153 ?        SW     0:00 [kseriod]
   190 ?        SW     0:00 [scsi_eh_0]
   191 ?        SW     0:00 [aacraid]
   204 ?        SW     0:18 [kjournald]
   520 ?        SW     0:00 [khubd]
  1043 ?        SW     0:00 [kjournald]
  1044 ?        SW     0:00 [kjournald]
  1045 ?        SW     0:06 [kjournald]
  1463 ?        S      0:00 syslogd -m 0
  1467 ?        S      0:00 klogd -x
  1859 ?        S      0:02 /usr/sbin/sshd
  1884 ?        S      0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
  1947 ?        S      0:00 crond
  2010 ?        S      0:00 proftpd: (accepting connections)
  2017 tty1     S      0:00 /sbin/mingetty tty1
  2018 tty2     S      0:00 /sbin/mingetty tty2
  2019 tty3     S      0:00 /sbin/mingetty tty3
  2020 tty4     S      0:00 /sbin/mingetty tty4
  2021 tty5     S      0:00 /sbin/mingetty tty5
  2022 tty6     S      0:00 /sbin/mingetty tty6
11707 ?        S      0:00 sshd: serge [priv]
11709 ?        S      0:01 sshd: serge@REDACTED/1
11710 pts/1    S      0:01 -bash
31265 pts/1    S      0:00 rxvt -sr -fg white -bg black -fn Clean -sl 300
31266 pts/0    S      0:00 bash
27564 ?        S      0:00 /usr/local/lib/erlang/erts-5.4.5/bin/epmd -daemon
27557 pts/0    R      0:00 ps -ax

klacke@REDACTED wrote:
> On Fri, Apr 22, 2005 at 10:05:23AM -0400, Serge Aleynikov wrote:
> 
>>Hi,
>>
>>I upgraded Erlang on one of our Linux servers to R10B-4, and started 
>>getting this error at startup.  This problem wasn't observed before the 
>>upgrade.
>>
>>
>>>erl -sname a
>>
>>{error_logger,{{2005,4,21},{21,30,39}},'Protocol: ~p: register error: 
>>~p~n',[inet_tcp,{timeout,{gen_server,call,[erl_epmd,{register,a,35269},15000]}}]}
>>{error_logger,{{2005,4,21},{21,30,39}},crash_report,
> 
> 
> .........
> 
> One of the early Erlang slogans 
> was: "Symolic information is always available".
> Somehow, that spung to my mind what I saw your higly _symbolic_
> error message :-)
> 
> 
> It does though look as if there is some trouble while
> registering the node name with epmd.
> Maybe incompatible epmd vsns ??, 'killall epmd' and retry.
> 
> 
> /klacke