[rabbitmq-discuss] RabbitMQ Completely Unusable

SixDegrees paulcarlisle at comcast.net
Sun Oct 9 19:28:15 BST 2011

I had Celery/RabbitMQ running perfectly on Friday. After a reboot, none of
the rabbitmqctl commands work; they all return the message:

Status of node rabbit at basalt ...
Error: unable to connect to node rabbit at basalt: nodedown
- nodes and their ports on basalt: [{rabbitmqctl4119,39973}]
- current node: rabbitmqctl4119 at basalt
- current node home dir: /var/lib/rabbitmq
- current node cookie hash: 21qdNRGvqYUEWK3+aXB7wA==

The port and nodename suffix are different each time, and the cookie hash
does not correspond to the one in /var/lib/rabbitmq/.erlang.cookie, nor can
I find any other instance of the cookie file on the machine. Hostname
'basalt' is listed in /etc/hosts under '  basalt'; this has not
been changed since Friday.

I have tried starting rabbitmq-server at runtime as a service; and at the
command line with no arguments and with the '-detached' argument, all with
similar results.

What do I have to do to recover my previously working system? Failing that,
what do I have to delete to get RabbitMQ back to a working, uninitialized
View this message in context: http://old.nabble.com/RabbitMQ-Completely-Unusable-tp32619934p32619934.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

More information about the rabbitmq-discuss mailing list