System limit bringing down rex and the VM

Musumeci, Antonio S <>
Wed Sep 8 15:35:35 CEST 2010


Is this an expected behavior? Shouldn't there be a way to more graciously handle this type of thing?

=ERROR REPORT==== 8-Sep-2010::09:28:26 ===
** Generic server rex terminating
** Last message in was {call,mnesia_lib,get_node_number,[],<0.55.0>}
** When Server state == {0,nil}
** Reason for termination ==
** {system_limit,[{erlang,spawn_opt,
                          [{erlang,apply,
                                   [#Fun<rpc.1.93176247>,[]],
                                   [monitor]}]},
                  {erlang,spawn_monitor,1},
                  {rpc,handle_call_call,6},
                  {gen_server,handle_msg,5},
                  {proc_lib,init_p_do_apply,3}]}

=CRASH REPORT==== 8-Sep-2010::09:28:26 ===
  crasher:
    initial call: rpc:init/1
    pid: <0.12.0>
    registered_name: rex
    exception exit: {system_limit,
                        [{erlang,spawn_opt,
                             [{erlang,apply,
                                  [#Fun<rpc.1.93176247>,[]],
                                  [monitor]}]},
                         {erlang,spawn_monitor,1},
                         {rpc,handle_call_call,6},
                         {gen_server,handle_msg,5},
                         {proc_lib,init_p_do_apply,3}]}
      in function  gen_server:terminate/6
    ancestors: [kernel_sup,<0.10.0>]
    messages: []
    links: [<0.11.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 377
    stack_size: 24
    reductions: 143
  neighbours:

=SUPERVISOR REPORT==== 8-Sep-2010::09:28:26 ===
     Supervisor: {local,kernel_sup}
     Context:    child_terminated
     Reason:     {system_limit,
                     [{erlang,spawn_opt,
                          [{erlang,apply,
                               [#Fun<rpc.1.93176247>,[]],
                               [monitor]}]},
                      {erlang,spawn_monitor,1},
                      {rpc,handle_call_call,6},
                      {gen_server,handle_msg,5},
                      {proc_lib,init_p_do_apply,3}]}
     Offender:   [{pid,<0.12.0>},
                  {name,rex},
                  {mfargs,{rpc,start_link,[]}},
                  {restart_type,permanent},
                  {shutdown,2000},
                  {child_type,worker}]


=SUPERVISOR REPORT==== 8-Sep-2010::09:28:26 ===
     Supervisor: {local,kernel_sup}
     Context:    shutdown
     Reason:     reached_max_restart_intensity
     Offender:   [{pid,<0.12.0>},
                  {name,rex},
                  {mfargs,{rpc,start_link,[]}},
                  {restart_type,permanent},
                  {shutdown,2000},
                  {child_type,worker}]


=ERROR REPORT==== 8-Sep-2010::09:28:26 ===
Mnesia(<mailto:>): ** ERROR ** mnesia_recover got unexpected info: {'EXIT',
                                                                   <0.84.0>,
                                                                   shutdown}

--------------------------------------------------------------------------
NOTICE: If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link: http://www.morganstanley.com/disclaimers. If you cannot access these links, please notify us by reply message and we will send the contents to you. By messaging with Morgan Stanley you consent to the foregoing.


More information about the erlang-questions mailing list