[rabbitmq-discuss] Cannot start or stop RabbitMQ using rabbitmqctl

tim tim at rabbitmq.com
Wed May 16 13:42:39 BST 2012


On 16/05/2012 13:24, mrtn wrote:
>
> Hi,
>
> I installed the latest RabbitMQ via macports on OS X 10.6.8, and have
> been trying to run it on localhost. However, after I started the
> server using 'sudo rabbitmq-server -detached', I cannot stop the
> server/node, nor can I start a new one (as expected). Below is the
> output: first, I try to start a new server but failed because there is
> already running; second, I then try to stop the existing server/node
> but get told it is already down. Can anyone point out what is going on
> here?!
>
> mrtn:MyLab mrtn$ sudo rabbitmq-server -detached
> Activating RabbitMQ plugins ...
> 0 plugins activated:
>
> node with name "rabbit" already running on "h002"
>
> DIAGNOSTICS
> ===========
>
> nodes in question: [rabbit at h002]
>
> hosts, their running nodes and ports:
> - h002: [{rabbit,62428},{rabbitmqprelaunch12073,54048}]
>
> current node details:
> - node name: rabbitmqprelaunch12073 at h002
> - home dir: /opt/local/var/lib/rabbitmq
> - cookie hash: q7VU0JjCd0VG7jOEF9Hf/g==
>
> mrtn:MyLab mrtn$ sudo rabbitmqctl stop
> Stopping and halting node rabbit at h002 ...
> Error: unable to connect to node rabbit at h002: nodedown
>
> DIAGNOSTICS
> ===========
>
> nodes in question: [rabbit at h002]
>
> hosts, their running nodes and ports:
> - h002: [{rabbit,62428},{rabbitmqctl12108,54053}]
>
> current node details:
> - node name: rabbitmqctl12108 at h002
> - home dir: /opt/local/var/lib/rabbitmq
> - cookie hash: q7VU0JjCd0VG7jOEF9Hf/g==
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Is the existing rabbit running with the same Erlang cookie as the new 
one? The cookie hash produced by rabbitmqctl is for the current node, 
not the one you're attempting to contact.

The list of nodes/ports on the given host indicates which Erlang nodes 
are up, but not necessarily whether they're allowed to connect to or 
not. Check your cookie and let us know how you get on.

Tim


More information about the rabbitmq-discuss mailing list