[Server-devel] Ejabberd CPU/RAM Spike -> Crashes

Devon Connolly devcon at gmail.com
Thu Dec 17 05:35:58 EST 2009


XS Version: 0.6
1 GB Physical Ram, 2GB Swap
154 XO's Registered, Any number connected when the problem happens, 0-XX
The XS is controlling dhcp but nothing out of the ordinary as far as  
leases are concerned.
No Active Antenna

# /home/idmgr/list_registration
http://pastebin.com/m762076bb

# ejabberdctl stats registeredusers
154

# ejabberdctl connected-users

032a8890f8a9731cfc611580524176a1f8f6c89d at schoolserver.notredame.sn/Telepathy
0a0c7fd971cdd25851ba34c9df66ef184590043a at schoolserver.notredame.sn/Telepathy
1c058ff553b654a3d808a3ffe95aadf4de841c77 at schoolserver.notredame.sn/Telepathy
26b8669a3e9387ac726296de07deced5aaf49985 at schoolserver.notredame.sn/Telepathy
2f596cc8d6977519411f5c8fcc65e751e8bd3b04 at schoolserver.notredame.sn/Telepathy
909785500a4fc5e14fe9f1cd7657e7ac3444022c at schoolserver.notredame.sn/Telepathy
9b2102f9af673393c9faa1f3565bd28773f48bc6 at schoolserver.notredame.sn/Telepathy
b4e5426593e58970c1b5dafa2adb39e4c3e59ea0 at schoolserver.notredame.sn/Telepathy
b7b58f3b01f49c8c652ddaedffd6faeef555bcb2 at schoolserver.notredame.sn/Telepathy
efb20aece0870421fc0f3facc58653bdac922d3d at schoolserver.notredame.sn/Telepathy
f9b21026d27589b02b894e221e5531cd1edd195a at schoolserver.notredame.sn/Telepathy

# olpc-netstatus
//The XO's are using gabble

After leaving it on all night, load averages hit 30....  It was  
unresponsive and any calls to ejabberdctl yielded the following error:

#ejabberdctl --node ejabberd at schoolserver connected-users
______________________________________________________________________________________________
{error_logger,{{2009,12,17},{10,0,25}},"Protocol: ~p: register error:  
~p~n",["inet_tcp",{{badmatch,{error,duplicate_name}},[{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,{{2009,12,17},{10,0,25}},crash_report,[[{pid,<0.20.0>},{registered_name,net_kernel},{error_info,{exit,{error,badarg},[{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},{initial_call,{net_kernel,init,['Argument__1']}},{ancestors,[net_sup,kernel_sup,<0.8.0>]},{messages,[]},{links,[#Port<0.84>,<0.17.0>]},{dictionary,[{longnames,false}]},{trap_exit,true},{status,running},{heap_size,610},{stack_size,23},{reductions,506}],[]]}
{error_logger,{{2009,12,17},{10,0,25}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{offender,[{pid,undefined},{name,net_kernel},{mfa,{net_kernel,start_link,[[ejabberdctl,shortnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
{error_logger,{{2009,12,17},{10,0,25}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,shutdown},{offender,[{pid,undefined},{name,net_sup},{mfa,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
{error_logger,{{2009,12,17},{10,0,25}},crash_report,[[{pid,<0.7.0>},{registered_name,[]},{error_info,{exit,{shutdown,{kernel,start,[normal,[]]}},[{application_master,init,4},{proc_lib,init_p_do_apply,3}]}},{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{ancestors,[<0.6.0>]},{messages,[{'EXIT',<0.8.0>,normal}]},{links,[<0.6.0>,<0.5.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,233},{stack_size,23},{reductions,123}],[]]}
{error_logger,{{2009,12,17},{10,0,26}},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: erl_crash.dump
Kernel pid terminated (application_controller)  
({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})


More information about the Server-devel mailing list