[rabbitmq-discuss] Mgmt API stopped reporting a lot of stuff

[carlhoerberg]

The second restart attempt of tiger03 puts the following in startup_err:

Crash dump was written to: erl_crash.dump
eheap_alloc: Cannot allocate 4454408120 bytes of memory (of type "heap").

The log file was filled with these during startup:
=ERROR REPORT==== 18-Apr-2013::23:40:10 ===
Discarding message {'$gen_call',{<0.27239.1>,#Ref<0.0.0.102362>},stat} from
<0.27239.1> to <0.5995.4> in an old incarnation (3) of this node (1)



When tiger03 was killed the first time tiger02 reported this in the sasl:

=CRASH REPORT==== 18-Apr-2013::23:11:42 ===
  crasher:
    initial call: application_master:init/4
    pid: <0.9.743>
    registered_name: []
    exception exit: {bad_return,
                     {{rabbit_mgmt_app,start,[normal,[]]},
                      {'EXIT',
                       {{shutdown,
                         [{{nodedown,rabbit at tiger03},
                           {gen_server,call,
                            [<6872.4529.0>,which_children,infinity]}}]},
                        {gen_server2,call,
                         [<0.47.743>,{init,<0.45.743>},infinity]}}}}}
      in function  application_master:init/4
    ancestors: [<0.8.743>]
    messages: [{'EXIT',<0.10.743>,normal}]
    links: [<0.8.743>,<0.7.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 377
    stack_size: 24
    reductions: 116
  neighbours:

=SUPERVISOR REPORT==== 18-Apr-2013::23:11:42 ===
     Supervisor: {local,rabbit_mgmt_sup}
     Context:    child_terminated
     Reason:     {shutdown,
                     [{{nodedown,rabbit at tiger03},
                       {gen_server,call,
                           [<6872.4529.0>,which_children,infinity]}}]}
     Offender:   [{pid,<0.47.743>},
                  {name,mirroring},
                  {mfa,
                      {mirrored_supervisor,start_internal,
                          [rabbit_mgmt_sup,
                           [{rabbit_mgmt_db,
                                {rabbit_mgmt_db,start_link,[]},
                                permanent,4294967295,worker,
                                [rabbit_mgmt_db]}]]}},
                  {restart_type,permanent},
                  {shutdown,4294967295},
                  {child_type,worker}]


=SUPERVISOR REPORT==== 18-Apr-2013::23:11:42 ===
     Supervisor: {local,rabbit_mgmt_sup}
     Context:    shutdown
     Reason:     reached_max_restart_intensity
     Offender:   [{pid,<0.47.743>},
                  {name,mirroring},
                  {mfa,
                      {mirrored_supervisor,start_internal,
                          [rabbit_mgmt_sup,
                           [{rabbit_mgmt_db,
                                {rabbit_mgmt_db,start_link,[]},
                                permanent,4294967295,worker,
                                [rabbit_mgmt_db]}]]}},
                  {restart_type,permanent},
                  {shutdown,4294967295},
                  {child_type,worker}]

And now it doesn't respond to "rabbitmqctl status" any longer either, a
"rabbitmqctl stop" gives the following in the log:

=INFO REPORT==== 18-Apr-2013::23:45:40 ===
Stopping RabbitMQ

=INFO REPORT==== 18-Apr-2013::23:45:40 ===
    application: rabbitmq_management_agent
    exited: stopped
    type: temporary

but nothing else. 



--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Mgmt-API-stopped-reporting-a-lot-of-stuff-tp26065p26093.html
Sent from the RabbitMQ mailing list archive at Nabble.com.