crash dump at ejabberd startup

tom <>
Tue Nov 16 11:14:01 CET 2010


Hello everybody in the Erlang universe,

I got stuck with a problem getting ejabberd to run in a FreeBSD8 Jail. 
Erlang and ejabberd were built using the Ports Collection (this week).

As far as I could learn from googling all this, the issue goes back to the 
erlang environment and abviously has something to do with "inet", TCP etc.. 
Well, even I know a bit about Unix I can't help myself with the error 
messages erlang spits out (no clue what these messages actually / precisely 
want to tell me):

ejabberd Start:

# ejabberdctl status
{error_logger,{{2010,11,16},{9,56,20}},"Protocol: ~p: register error: ~p~n",
["inet_tcp",{{badmatch,{error,epmd_close}},[{inet_tcp_dist,listen,1},
{net_kernel,start_protos,4},{net_kernel,start_protos,3},
{net_kernel,init_node,2},{net_kernel,init,1},{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]}]}
{error_logger,{{2010,11,16},{9,56,20}},crash_report,[[{initial_call,
{net_kernel,init,['Argument__1']}},{pid,<0.19.0>},{registered_name,[]},
{error_info,{exit,{error,badarg},[{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]}},{ancestors,[net_sup,kernel_sup,<0.9.0>]},
{messages,[]},{links,[#Port<0.101>,<0.16.0>]},{dictionary,
[{longnames,false}]},{trap_exit,true},{status,running},{heap_size,610},
{stack_size,24},{reductions,489}],[]]}
{error_logger,{{2010,11,16},{9,56,20}},supervisor_report,[{supervisor,
{local,net_sup}},{errorContext,start_error},{reason,
{'EXIT',nodistribution}},{offender,[{pid,undefined},{name,net_kernel},
{mfargs,{net_kernel,start_link,[['',shortnames]]}},
{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
{error_logger,{{2010,11,16},{9,56,20}},supervisor_report,[{supervisor,
{local,kernel_sup}},{errorContext,start_error},{reason,shutdown},{offender,
[{pid,undefined},{name,net_sup},{mfargs,{erl_distribution,start_link,[]}},
{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
{error_logger,{{2010,11,16},{9,56,20}},std_info,[{application,kernel},
{exited,{shutdown,{kernel,start,[normal,[]]}}},{type,permanent}]}
{"Kernel pid 
terminated",application_controller,"{application_start_failure,kernel,
{shutdown,{kernel,start,[normal,[]]}}}"}

Crash dump was written to: /var/log/ejabberd/erl_crash_20101116-095620.dump
Kernel pid terminated (application_controller) 
({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})

Well, I wouldn't be surprised if all this had to do with the mysterious 
"inetrc" configuration file. The example from the FreeBSD port contains:

# cat inetrc
{lookup,["file","native"]}.
{host,{127,0,0,1}, ["localhost","hostalias"]}.
{file, resolv, "/etc/resolv.conf"}.

I already tried some hints from what could be found via Google - but 
nonetheless didn't succeed or even made progress.

The funny thing is, I once had ejabberd running as a test system in another 
FreeBSD Jail but unfortunately did not note all details before wiping that 
old host.

So, anybody out there capable to give any hints ?
Understanding the problem might be 90% of getting the solution ...

Many thanks in advance !

kind regards
Tom



More information about the erlang-questions mailing list