[rabbitmq-discuss] RabbitMQ 3.2.4 fails to start if management plugin enabled
Junius Wang
wangjunbo924 at gmail.com
Thu Mar 6 01:37:25 GMT 2014
No, not in a cluster. Sasl log tells:
=SUPERVISOR REPORT==== 5-Mar-2014::10:31:09 ===
Supervisor: {local,rabbit_mgmt_sup}
Context: child_terminated
Reason: {shutdown,
[{{badmatch,[]},
[{mirrored_supervisor,child,2},
{mirrored_supervisor,with_exit_handler,2},
{mirrored_supervisor,check_start,4},
{mnesia_tm,apply_fun,3},
{mnesia_tm,execute_transaction,5},
{rabbit_misc,'-execute_mnesia_transaction/1-fun-0-',1},
{worker_pool_worker,handle_call,3},
{gen_server2,handle_msg,2}]}]}
Offender: [{pid,<0.353.0>},
{name,mirroring},
{mfargs,
{mirrored_supervisor,start_internal,
[rabbit_mgmt_sup,
#Fun<rabbit_misc.execute_mnesia_transaction.1>,
[{rabbit_mgmt_db,
{rabbit_mgmt_db,start_link,[]},
permanent,4294967295,worker,
[rabbit_mgmt_db]}]]}},
{restart_type,permanent},
{shutdown,4294967295},
{child_type,worker}]
=SUPERVISOR REPORT==== 5-Mar-2014::10:31:09 ===
Supervisor: {local,rabbit_mgmt_sup}
Context: shutdown
Reason: reached_max_restart_intensity
Offender: [{pid,<0.353.0>},
{name,mirroring},
{mfargs,
{mirrored_supervisor,start_internal,
[rabbit_mgmt_sup,
#Fun<rabbit_misc.execute_mnesia_transaction.1>,
[{rabbit_mgmt_db,
{rabbit_mgmt_db,start_link,[]},
permanent,4294967295,worker,
[rabbit_mgmt_db]}]]}},
{restart_type,permanent},
{shutdown,4294967295},
{child_type,worker}]
=SUPERVISOR REPORT==== 5-Mar-2014::10:31:09 ===
Supervisor: {local,rabbit_mgmt_sup_sup}
Context: start_error
Reason: {'EXIT',
{{shutdown,
[{{badmatch,[]},
[{mirrored_supervisor,child,2},
{mirrored_supervisor,with_exit_handler,2},
{mirrored_supervisor,check_start,4},
{mnesia_tm,apply_fun,3},
{mnesia_tm,execute_transaction,5},
{rabbit_misc,
'-execute_mnesia_transaction/1-fun-0-',1},
{worker_pool_worker,handle_call,3},
{gen_server2,handle_msg,2}]}]},
{gen_server2,call,
[<0.353.0>,{init,<0.351.0>},infinity]}}}
Offender: [{pid,undefined},
{name,rabbit_mgmt_sup},
{mfargs,{rabbit_mgmt_sup,start_link,[]}},
{restart_type,temporary},
{shutdown,4294967295},
{child_type,supervisor}]
=CRASH REPORT==== 5-Mar-2014::10:31:09 ===
crasher:
initial call: application_master:init/4
pid: <0.314.0>
registered_name: []
exception exit: {{shutdown,
{failed_to_start_child,rabbit_mgmt_sup,
{'EXIT',
{{shutdown,
[{{badmatch,[]},
[{mirrored_supervisor,child,2},
{mirrored_supervisor,with_exit_handler,2},
{mirrored_supervisor,check_start,4},
{mnesia_tm,apply_fun,3},
{mnesia_tm,execute_transaction,5},
{rabbit_misc,
'-execute_mnesia_transaction/1-fun-0-',1},
{worker_pool_worker,handle_call,3},
{gen_server2,handle_msg,2}]}]},
{gen_server2,call,
[<0.353.0>,{init,<0.351.0>},infinity]}}}}},
{rabbit_mgmt_app,start,[normal,[]]}}
in function application_master:init/4
ancestors: [<0.313.0>]
messages: [{'EXIT',<0.315.0>,normal}]
links: [<0.313.0>,<0.7.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 610
stack_size: 24
reductions: 109
neighbours:
-----Original Message-----
From: Simon MacMullen [mailto:simon at rabbitmq.com]
Sent: Wednesday, March 05, 2014 11:28 PM
To: Discussions about RabbitMQ; Junius Wang
Subject: Re: [rabbitmq-discuss] RabbitMQ 3.2.4 fails to start if management
plugin enabled
Is this in a cluster?
What does /var/log/rabbitmq/rabbit at rabbit4-sasl.log show?
Cheers, Simon
On 05/03/14 10:32, Junius Wang wrote:
> Hi,
>
> I tried the latest release 3.2.4. The initial start succeeded after
> installed. However, as long as I enabled the management plugin(by
> "rabbitmq_plugins enable rabbitmq_management") ,RabbitMQ cannot start
> anymore. I'm CentOS 6.4 with erlong R14B04(erts-5.8.5). What's the
> matter?
>
> Before the plugin enabled, RabbitMQ is runing:
>
> [root at rabbit4 rabbitmq]# sudo rabbitmqctl status
>
> Status of node rabbit at rabbit4 ...
>
> [{pid,28255},
>
> {running_applications,[{rabbit,"RabbitMQ","3.2.4"},
>
> {os_mon,"CPO CXC 138 46","2.2.7"},
>
> {xmerl,"XML parser","1.2.10"},
>
> {mnesia,"MNESIA CXC 138 12","4.5"},
>
> {sasl,"SASL CXC 138 11","2.1.10"},
>
> {stdlib,"ERTS CXC 138 10","1.17.5"},
>
> {kernel,"ERTS CXC 138 10","2.14.5"}]},
>
> {os,{unix,linux}},
>
> {erlang_version,"Erlang R14B04 (erts-5.8.5) [source] [64-bit] [rq:1]
> [async-threads:30] [kernel-poll:true]\n"},
>
> {memory,[{total,27470168},
>
> {connection_procs,2648},
>
> {queue_procs,5296},
>
> {plugins,0},
>
> {other_proc,9321128},
>
> {mnesia,58928},
>
> {mgmt_db,0},
>
> {msg_index,21112},
>
> {other_ets,775152},
>
> {binary,6256},
>
> {code,14561678},
>
> {atom,1360113},
>
> {other_system,1357857}]},
>
> {vm_memory_high_watermark,0.4},
>
> {vm_memory_limit,247676928},
>
> {disk_free_limit,50000000},
>
> {disk_free,5879087104},
>
> {file_descriptors,[{total_limit,924},
>
> {total_used,3},
>
> {sockets_limit,829},
>
> {sockets_used,1}]},
>
> {processes,[{limit,1048576},{used,124}]},
>
> {run_queue,0},
>
> {uptime,16}]
>
> ...done.
>
> After it's enabled. RabbitMQ fails to start:
>
> [root at rabbit4 rabbitmq]# cat /var/log/rabbitmq/startup_log
>
> RabbitMQ 3.2.4. Copyright (C) 2007-2013 GoPivotal, Inc.
>
> ## ## Licensed under the MPL. See http://www.rabbitmq.com/
>
> ## ##
>
> ########## Logs: /var/log/rabbitmq/rabbit at rabbit4.log
>
> ###### ## /var/log/rabbitmq/rabbit at rabbit4-sasl.log
>
> ##########
>
> Starting broker...
>
> BOOT FAILED
>
> ===========
>
> Error description:
>
> {could_not_start,rabbitmq_management,
>
> {{shutdown,
>
> {failed_to_start_child,rabbit_mgmt_sup,
>
> {'EXIT',
>
> {{shutdown,
>
> [{{badmatch,[]},
>
> [{mirrored_supervisor,child,2},
>
>
> {mirrored_supervisor,with_exit_handler,2},
>
> {mirrored_supervisor,check_start,4},
>
> {mnesia_tm,apply_fun,3},
>
> {mnesia_tm,execute_transaction,5},
>
> {rabbit_misc,
>
>
> '-execute_mnesia_transaction/1-fun-0-',1},
>
> {worker_pool_worker,handle_call,3},
>
> {gen_server2,handle_msg,2}]}]},
>
> {gen_server2,call,
>
> [<0.353.0>,{init,<0.351.0>},infinity]}}}}},
>
> {rabbit_mgmt_app,start,[normal,[]]}}}
>
> Log files (may contain more information):
>
> /var/log/rabbitmq/rabbit at rabbit4.log
>
> /var/log/rabbitmq/rabbit at rabbit4-sasl.log
>
> {"init terminating in
> do_boot",{rabbit,failure_during_boot,{could_not_start,rabbitmq_managem
> ent,{{shutdown,{failed_to_start_child,rabbit_mgmt_sup,{'EXIT',{{shutdo
> wn,[{{badmatch,[]},[{mirrored_supervisor,child,2},{mirrored_supervisor
> ,with_exit_handler,2},{mirrored_supervisor,check_start,4},{mnesia_tm,a
> pply_fun,3},{mnesia_tm,execute_transaction,5},{rabbit_misc,'-execute_m
> nesia_transaction/1-fun-0-',1},{worker_pool_worker,handle_call,3},{gen
> _server2,handle_msg,2}]}]},{gen_server2,call,[<0.353.0>,{init,<0.351.0
> >},infinity]}}}}},{rabbit_mgmt_app,start,[normal,[]]}}}}}
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
--
Simon MacMullen
RabbitMQ, Pivotal
More information about the rabbitmq-discuss
mailing list