Changing the domain, I still get the following error when it tries (and
fails to shutdown ejabberd).
___________________________________________________________________________
Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller)
({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})
{error_logger,{{2009,12,19},{12,19,16}},"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,19},{12,19,16}},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,505}],[]]}
{error_logger,{{2009,12,19},{12,19,16}},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,19},{12,19,16}},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,19},{12,19,16}},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,19},{12,19,16}},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,[]]}}})
______________________________________________________________________________
Beam is still consuming 100% of the cpu after a few minutes. I'm going to
leave that script running to see what it does over the next few hours.
I imagine I now have to re-register all XO's?
On Sat, Dec 19, 2009 at 10:59 AM, Devon Connolly <dev...@gmail.com> wrote:
>
> Here is another example after it has been running all night.
>
> http://pastebin.com/m11537281
>
> As you can see, these runaway beam processes vary greatly in there RAM
> usage. Also, they are always using 100% of the cpu.
>
> I will try to clear the DB now and see what happens.
>
>
>
> On Fri, Dec 18, 2009 at 12:51 PM, Martin Langhoff <
> martin.langh...@gmail.com> wrote:
>
>> On Fri, Dec 18, 2009 at 1:37 PM, Devon Connolly <dev...@gmail.com> wrote:
>> > Anyway, back on topic... Here is that script slightly modified running
>> on
>> > a fresh boot. I'm going to leave this looping and post the file to
>> > pastebin. Here is an initial output after only like 10 minutes. It
>> will
>> > get more interesting over time. I'll paste another later this
>> afternoon.
>>
>> outrageous. beam should have only ~40MB in use, total.
>>
>> if you 'clear' the mnesia db as i suggested (keep a copy for
>> forensics!), does it get better?
>>
>>
>>
>> m
>> --
>> martin.langh...@gmail.com
>> mar...@laptop.org -- School Server Architect
>> - ask interesting questions
>> - don't get distracted with shiny stuff - working code first
>> - http://wiki.laptop.org/go/User:Martinlanghoff
>>
>
>
>
_______________________________________________
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel
