Thu Mar 14 15:04:54 GMT 2013
running, though you seem to be unable to contact it. Check if the
connection attempts show up in the broker logfile - perhaps you are not
using the correct cookie file.
> sudo rabbitmqctl stop
> And it show: Error: unable to connect to node rabbit@ mydomain: nodedown
If that doesn't work and you can't establish contact with the broker
using the normal admin channel then killing the Erlang process is the
simplest way to proceed. Check for "beam" or "beam.smp" processes
associated with RabbitMQ and send a kill signal.
More information about the rabbitmq-discuss