[rabbitmq-discuss] Rabbitmqctl issues

[Edwin Fine]

Would you like to try this?

Please ensure that you are using the same Erlang cookie that Rabbit was
started with. This is in a file is named $HOME/.erlang.cookie where $HOME is
the directory of the user that started rabbitmq. If you try to run commands
that connect to the rabbitmq Erlang node, using a different user name, even
as root, if it does not have the same cookie file, the commands will fail.

It's best to control rabbit exclusively as one user, for example as the
rabbit user.

Hope this helps,
Edwin

On Wed, Oct 1, 2008 at 4:52 PM, Alex Clemesha <clemesha at gmail.com> wrote:

> Hi,
>
> I also run into the same thing (actually happened ~15 minutes ago), I'm
> using Ubuntu 8.04.
> (installed RabbitMQ by adding the relevant line to /etc/apt/source.list,
> then using apt-get).
>
> I usually just find the relevant processes and kill them, then run
> 'rabbitmq-server -detached'
> to start things back up.
>
> I just assumed I was missing something (maybe I still am :-)
>
> thanks
> -Alex
>
>
> On Wed, Oct 1, 2008 at 1:29 PM, Peter Kieltyka <peter.kieltyka at gmail.com>wrote:
>
>> Hello everyone,
>>
>> For the longest time, I've struggled to be able to control the server
>> to do basic start/stop/restart commands.
>>
>> Currently on my production server I am running Debian Etch where I
>> followed the instructions at http://www.rabbitmq.com/debian.html to
>> install Rabbit.
>>
>> Running the rabbitmq-server or rabbitmq-multi start_all 1 commands
>> will bring the server online, however to stop it, or add a user none
>> of the scripts work. I am always presented with an error, bad_node.
>>
>> I.e.
>>
>> Creating user "patbroker" ...
>> rabbit_control action add_user failed:
>> {badrpc,nodedown}
>>
>> However, I can confirm that Rabbit is running fine because my
>> application is working just fine. I've even tried explicitly
>> specifying the -n rabbit at broker (hostname -s returns broker).
>>
>> The same goes for stopping the server, either using /etc/init.d/
>> rabbitmq-server stop, or calling "rabbitmq-multi stop_all" directly
>> will result in:
>>
>> Stopping all nodes...
>>
>> rabbit_multi action stop_all failed:
>> no_nodes_running
>>
>> Thanks.
>>
>> Peter
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>
>
>
> --
> Alex Clemesha
> clemesha.org
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20081001/c134469a/attachment.htm