[rabbitmq-discuss] RabbitMQ does not start with rabbit-status plugin - broker is running
Steverding, Kai
Kai.Steverding at gws.ms
Wed Jun 2 10:19:57 BST 2010
Hi !
Without plugins, everything is fine :
root at rabbit-cl1:~# rabbitmq-deactivate-plugins
root at rabbit-cl1:~# /etc/init.d/rabbitmq-server restart
Restarting rabbitmq-server: No nodes running
SUCCESS
rabbitmq-server.
root at rabbit-cl1:~# rabbitmqctl status
Status of node 'rabbit at rabbit-cl1' ...
[{running_applications,[{rabbit,"RabbitMQ","1.7.2"},
{mnesia,"MNESIA CXC 138 12","4.4.12"},
{os_mon,"CPO CXC 138 46","2.2.4"},
{sasl,"SASL CXC 138 11","2.1.8"},
{stdlib,"ERTS CXC 138 10","1.16.4"},
{kernel,"ERTS CXC 138 10","2.13.4"}]},
{nodes,['rabbit at rabbit-cl1']},
{running_nodes,['rabbit at rabbit-cl1']}]
...done.
And now for the logs :
cat /var/log/rabbitmq/rabbit.log
=INFO REPORT==== 2-Jun-2010::11:16:25 ===
Memory limit set to 803MB.
=INFO REPORT==== 2-Jun-2010::11:16:25 ===
Rolling persister log to "/var/lib/rabbitmq/mnesia/rabbit/rabbit_persister.LOG.previous"
=INFO REPORT==== 2-Jun-2010::11:16:25 ===
started TCP Listener on 0.0.0.0:5672
=INFO REPORT==== 2-Jun-2010::11:16:25 ===
application: rabbit_status
exited: {shutdown,{rabbit_status_app,start,[normal,[]]}}
type: permanent
=INFO REPORT==== 2-Jun-2010::11:16:25 ===
stopped TCP Listener on 0.0.0.0:5672
-----------------------------------------------------------------------------------------------
cat /var/log/rabbitmq/rabbit-sasl.log
=CRASH REPORT==== 2-Jun-2010::11:16:25 ===
crasher:
initial call: rabbit_status_web:init/1
pid: <0.156.0>
registered_name: []
exception exit: {undef,[{httpd_util,rfc1123_date,[{{2010,6,2},{9,16,25}}]},
{rabbit_status_web,internal_update,1},
{rabbit_status_web,init,1},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]}
in function gen_server:init_it/6
ancestors: [rabbit_status_sup,<0.154.0>]
messages: []
links: [<0.155.0>]
dictionary: []
trap_exit: false
status: running
heap_size: 6765
stack_size: 24
reductions: 13565
neighbours:
=SUPERVISOR REPORT==== 2-Jun-2010::11:16:25 ===
Supervisor: {local,rabbit_status_sup}
Context: start_error
Reason: {undef,[{httpd_util,rfc1123_date,[{{2010,6,2},{9,16,25}}]},
{rabbit_status_web,internal_update,1},
{rabbit_status_web,init,1},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]}
Offender: [{pid,undefined},
{name,rabbit_status_web},
{mfa,{rabbit_status_web,start_link,[]}},
{restart_type,permanent},
{shutdown,5000},
{child_type,worker}]
----------------------------------------------------------------------------------------------------
cat /var/log/rabbitmq/startup_log
Starting all nodes...
Starting node rabbit at rabbit-cl1...
+---+ +---+
| | | |
| | | |
| | | |
| +---+ +-------+
| |
| RabbitMQ +---+ |
| | | |
| v1.7.2 +---+ |
| |
+-------------------+
AMQP 8-0
Copyright (C) 2007-2010 LShift Ltd., Cohesive Financial Technologies LLC., and Rabbit Technologies Ltd.
Licensed under the MPL. See http://www.rabbitmq.com/
node : rabbit at rabbit-cl1
app descriptor: /usr/lib/rabbitmq/lib/rabbitmq_server-1.7.2/sbin/../ebin/rabbit.app
home dir : /var/lib/rabbitmq
cookie hash : TIQTKMN1LFm80SCVc+2Upw==
log : /var/log/rabbitmq/rabbit.log
sasl log : /var/log/rabbitmq/rabbit-sasl.log
database dir : /var/lib/rabbitmq/mnesia/rabbit
starting internal event notification system ...done
starting logging server ...done
starting database ...done
-- kernel ready
starting alarm handler ...done
starting queue supervisor ...done
starting node monitor ...done
starting cluster router ...done
-- core initialized
starting empty DB check ...done
starting codec correctness check ...done
starting exchange recovery ...done
starting queue recovery ...done
starting persister ...done
starting guid generator ...done
-- message delivery logic ready
starting error log relay ...done
starting networking ...done
-- network listeners available
broker running
{"Kernel pid terminated",application_controller,"{application_start_failure,rabbit_status,{shutdown,{rabbit_status_app,start,[normal,[]]}}}"}
--------------------------------------------------------------------------------------------------------
cat /var/log/rabbitmq/startup_err
Erlang has closed
Error: {node_start_failed,normal}
Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,rabbit_status,{shutdown,{rabbit_status_app,start,[normal,[]]}}})
Mit freundlichen Grüßen
Kai Steverding
_________________________________________________
GWS Gesellschaft für Warenwirtschafts-Systeme mbH
Krögerweg 10 - 48155 Münster
Kai Steverding
Branchensoftware-Entwicklung
Tel: +49 (251) 7000-02
Fax: +49 (251) 7000-3999
mailto:Kai.Steverding at gws.ms
Internet: http://www.gws.ms
GWS Gesellschaft für Warenwirtschafts-Systeme mbH
Münster, München, Nürnberg, Leonberg
Geschäftsführer: Dipl. Betriebswirt Helmut Benefader
Sitz: Münster (Westf.)
Amtsgericht Münster HRB 3844
-----Ursprüngliche Nachricht-----
Von: Marek Majkowski [mailto:majek04 at gmail.com]
Gesendet: Dienstag, 1. Juni 2010 17:18
An: Steverding, Kai
Cc: rabbitmq-discuss at lists.rabbitmq.com
Betreff: Re: [rabbitmq-discuss] RabbitMQ does not start with rabbit-status plugin - broker is running
2010/6/1 Steverding, Kai <Kai.Steverding at gws.ms>:
> Strange !
> I did the same on another Ubuntu system without rabbit and get the same error. I followed your instructions step by step
That's strange.
Can you attach following logs (if they aren't too big):
/var/log/rabbitmq/rabbit.log
/var/log/rabbitmq/rabbit-sasl.log
/var/log/rabbitmq/startup_log
/var/log/rabbitmq/startup_err
Do you get the same issue without any plugins? To check:
sudo rabbitmq-deactivate-plugins
sudo /etc/init.d/rabbitmq-server restart
More information about the rabbitmq-discuss
mailing list