[rabbitmq-discuss] Rabbitmq-server Fails to Start

Joel Friedly joelfriedly at gmail.com
Tue Jul 3 00:11:46 BST 2012


>
> $ sudo service rabbitmq-server start
> Starting rabbitmq-server: FAILED - check /var/log/rabbitmq/startup_{log, 
> _err}
> rabbitmq-server.

 
The log file shows that everything started properly, and the error file 
only says that rabbitmq-server failed to start:

Activating RabbitMQ plugins ...
> 0 plugins activated:
>
> +---+   +---+
> |   |   |   |
> |   |   |   |
> |   |   |   |
> |   +---+   +-------+
> |                   |
> | RabbitMQ  +---+   |
> |           |   |   |
> |   v2.5.0  +---+   |
> |                   |
> +-------------------+
> AMQP 0-9-1 / 0-9 / 0-8
> Copyright (C) 2007-2011 VMware, Inc.
> Licensed under the MPL.  See http://www.rabbitmq.com/
> node           : rabbit at ubuntu-vm
> app descriptor : 
> /usr/lib/rabbitmq/lib/rabbitmq_server-2.5.0/sbin/../ebin/rabbit.app
> home dir       : /var/lib/rabbitmq
> config file(s) : (none)
> cookie hash    : Eg8kv9KaWD54peNHomznOw==
> log            : /var/log/rabbitmq/rabbit at ubuntu-vm.log
> sasl log       : /var/log/rabbitmq/rabbit at ubuntu-vm-sasl.log
> database dir   : /var/lib/rabbitmq/mnesia/rabbit at ubuntu-vm
> erlang version : 5.8.3
> -- rabbit boot start
> starting file handle cache server                                     
> ...done
> starting worker pool                                                 
>  ...done
> starting database                                                     
> ...done
> starting codec correctness check                                     
>  ...done
> -- external infrastructure ready
> starting plugin registry                                             
>  ...done
> starting auth mechanism cr-demo                                       
> ...done
> starting auth mechanism amqplain                                     
>  ...done
> starting auth mechanism plain                                         
> ...done
> starting statistics event manager                                     
> ...done
> starting logging server                                               
> ...done
> starting exchange type direct                                         
> ...done
> starting exchange type fanout                                         
> ...done
> starting exchange type headers                                       
>  ...done
> starting exchange type topic                                         
>  ...done
> -- kernel ready
> starting alarm handler                                               
>  ...done
> starting node monitor                                                 
> ...done
> starting cluster delegate                                             
> ...done
> starting guid generator                                               
> ...done
> starting memory monitor                                               
> ...done
> -- core initialized
> starting empty DB check                                               
> ...done
> starting exchange, queue and binding recovery                         
> ...done
> -- message delivery logic ready
> starting error log relay                                             
>  ...done
> starting networking                                                   
> ...done
> starting direct_client                                               
>  ...done
> starting notify cluster nodes                                         
> ...done
> broker running


Error file:

Mon Jul  2 15:29:32 PDT 2012 - rabbitmq failed to start


Running `ps aux | grep rabbit` after a failed start shows that the 
processes seem to be running normally though:

$ ps aux | grep rabbit
> rabbitmq 20611  0.0  0.0   6808   324 ?        S    15:02   0:01 
> /usr/lib/erlang/erts-5.8.3/bin/epmd -daemon
> root     22617  0.0  0.0   4272   580 ?        Ss   15:29   0:00 /bin/sh 
> /usr/sbin/rabbitmq-server
> rabbitmq 22626  0.0  0.0  44804  1388 ?        S    15:29   0:00 su 
> rabbitmq -s /bin/sh -c /usr/lib/rabbitmq/bin/rabbitmq-server 
> rabbitmq 22627  0.0  0.0   4272   584 ?        S    15:29   0:00 sh -c 
> /usr/lib/rabbitmq/bin/rabbitmq-server 
> rabbitmq 22628  0.9  1.2  97360 26564 ?        Sl   15:29   0:07 
> /usr/lib/erlang/erts-5.8.3/bin/beam.smp -W w -K true -A30 -P 1048576 -- 
> -root /usr/lib/erlang -progname erl -- -home /var/lib/rabbitmq -- -noshell 
> -noinput -sname rabbit at ubuntu-vm -boot 
> /var/lib/rabbitmq/mnesia/rabbit at ubuntu-vm-plugins-expand/rabbit -kernel 
> inet_default_connect_options [{nodelay,true}] -sasl errlog_type error 
> -kernel error_logger {file,"/var/log/rabbitmq/rabbit at ubuntu-vm.log"} -sasl 
> sasl_error_logger {file,"/var/log/rabbitmq/rabbit at ubuntu-vm-sasl.log"} 
> -os_mon start_cpu_sup true -os_mon start_disksup false -os_mon start_memsup 
> false -mnesia dir "/var/lib/rabbitmq/mnesia/rabbit at ubuntu-vm"
> rabbitmq 22724  0.0  0.0   4164   324 ?        Ss   15:29   0:00 
> /usr/lib/erlang/lib/os_mon-2.2.5/priv/bin/cpu_sup
> rabbitmq 22725  0.0  0.0   6776   344 ?        Ss   15:29   0:00 
> inet_gethost 4
> rabbitmq 22726  0.0  0.0   8876   636 ?        S    15:29   0:00 
> inet_gethost 4
> joel     22805  0.0  0.0   9252   872 pts/0    R+   15:42   0:00 grep 
> rabbit


(My user is 'joel'.)

Running a `rabbitmqctl status` at this point shows that the broker is 
running:

$ sudo rabbitmqctl status
> Status of node 'rabbit at ubuntu-vm' ...
> [{pid,22628},
>  {running_applications,[{rabbit,"RabbitMQ","2.5.0"},
>                         {os_mon,"CPO  CXC 138 46","2.2.5"},
>                         {sasl,"SASL  CXC 138 11","2.1.9.3"},
>                         {mnesia,"MNESIA  CXC 138 12","4.4.17"},
>                         {stdlib,"ERTS  CXC 138 10","1.17.3"},
>                         {kernel,"ERTS  CXC 138 10","2.14.3"}]},
>  {os,{unix,linux}},
>  {erlang_version,"Erlang R14B02 (erts-5.8.3) [source] [64-bit] [smp:3:3] 
> [rq:3] [async-threads:30] [kernel-poll:true]\n"},
>  {memory,[{total,24305496},
>           {processes,9824640},
>           {processes_used,9821704},
>           {system,14480856},
>           {atom,1108281},
>           {atom_used,1096596},
>           {binary,6944},
>           {code,10828669},
>           {ets,692904}]}]
> ...done.


At this point, attempting a `sudo service rabbitmq-server restart` fails, 
with the same error message as starting the server.
Stopping the server via any of service rabbitmq-server stop, rabbitmqctl 
stop, or rabbitmqctl stop_app works fine, and I can reset nodes as 
expected, but starting the server always reports failure.

For reference, here's the output from `sudo service rabbitmqctl report`:

$ sudo rabbitmqctl report
> Reporting server status on {{2012,7,2},{22,53,37}}
> Status of node 'rabbit at ubuntu-vm' ...
> [{pid,23209},
>  {running_applications,[{rabbit,"RabbitMQ","2.5.0"},
>                         {os_mon,"CPO  CXC 138 46","2.2.5"},
>                         {sasl,"SASL  CXC 138 11","2.1.9.3"},
>                         {mnesia,"MNESIA  CXC 138 12","4.4.17"},
>                         {stdlib,"ERTS  CXC 138 10","1.17.3"},
>                         {kernel,"ERTS  CXC 138 10","2.14.3"}]},
>  {os,{unix,linux}},
>  {erlang_version,"Erlang R14B02 (erts-5.8.3) [source] [64-bit] [smp:3:3] 
> [rq:3] [async-threads:30] [kernel-poll:true]\n"},
>  {memory,[{total,24464720},
>           {processes,9917040},
>           {processes_used,9914104},
>           {system,14547680},
>           {atom,1108281},
>           {atom_used,1096530},
>           {binary,72472},
>           {code,10828669},
>           {ets,692760}]}]
> Cluster status of node 'rabbit at ubuntu-vm' ...
>
> [{nodes,[{disc,['rabbit at ubuntu-vm']}]},{running_nodes,['rabbit at ubuntu-vm']}]
> Application environment of node 'rabbit at ubuntu-vm' ...
> [{auth_backends,[rabbit_auth_backend_internal]},
>  {auth_mechanisms,['PLAIN','AMQPLAIN']},
>  {backing_queue_module,rabbit_variable_queue},
>  {cluster_nodes,[]},
>  {collect_statistics,none},
>  {default_permissions,[<<".*">>,<<".*">>,<<".*">>]},
>  {delegate_count,16},
>  {frame_max,131072},
>  {included_applications,[]},
>  {msg_store_file_size_limit,16777216},
>  {msg_store_index_module,rabbit_msg_store_ets_index},
>  {persister_hibernate_after,10000},
>  {persister_max_wrap_entries,500},
>  {queue_index_max_journal_entries,262144},
>  {server_properties,[]},
>  {ssl_listeners,[]},
>  {ssl_options,[]},
>  {tcp_listen_options,[binary,
>                       {packet,raw},
>                       {reuseaddr,true},
>                       {backlog,128},
>                       {nodelay,true},
>                       {exit_on_close,false}]},
>  {tcp_listeners,[5672]},
>  {trace_vhosts,[]},
>  {vm_memory_high_watermark,0.4}]
> Connections:
> Channels:
> Queues on /:
> Exchanges on /:
> name type durable auto_delete internal arguments
> amq.direct direct true false false []
> amq.topic topic true false false []
> amq.rabbitmq.trace topic true false false []
> amq.rabbitmq.log topic true false false []
> amq.fanout fanout true false false []
> amq.headers headers true false false []
> direct true false false []
> amq.match headers true false false []
> Bindings on /:
> Consumers on /:
> Permissions on /:
> user configure write read
> guest .* .* .*
> End of server status report
> ...done.


-----------------------------------

This problem started pretty randomly.  I've been using rabbitmq for quite a 
while but running my test suite failed today and I can't think of anything 
different that I've done.  
I've also attempted rebooting and purging/reinstalling.  This is all 
running on an Ubuntu VM, which could potentially cause problems, but 
shouldn't.  If you guys don't have any suggestions, I guess my next step 
will be to try reinstalling the VM.


Thanks for any help,
Joel Friedly
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120702/8c7c39ba/attachment.htm>


More information about the rabbitmq-discuss mailing list