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

Wed May 16 14:14:11 BST 2012

Hi Tim,

Thanks for getting back to me. I am new to rabbitmq so not very familiar
with the details you're asking for.

Here is what I see in /opt/local/var/lib/rabbitmq/.erlang.cookie:

QFZXZBPOMTJNACQIMJOT

and sudo rabbitmqctl status gives me:

Status of 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},{rabbitmqctl12565,55147}]

current node details:
- node name: rabbitmqctl12565 at h002
- home dir: /opt/local/var/lib/rabbitmq
- cookie hash: q7VU0JjCd0VG7jOEF9Hf/g==

I installed rabbitmq by following the instructions given here:
http://www.rabbitmq.com/install-macports.html, after which I ran sudo
rabbitmq-server -detached to start the server. Now I want to stop the
server using sudo rabbitmqctl stop, but it simply does not allow me to do
so by the looks of it.

I wonder what causes this kind of behavior? Am I running *multiple*
rabbitmq servers/nodes on my machine now, and somehow I am not allowed to
access some of them? Your help is much appreciated. Thanks.

Best,
Merton

On Wed, May 16, 2012 at 8:42 AM, tim <tim at rabbitmq.com> wrote:

> 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<rabbitmq-discuss at lists.rabbitmq.com>
>> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120516/e6515d3c/attachment.htm>