Comments on: On rabbitmqctl and badrpc,nodedown

By: Vincent

Vincent — Tue, 23 Jun 2009 00:57:41 +0000

I found a solution to a related issue which may be helpful to mention.

I was trying to run rabbit after migrating an existing user account. Status kept listing my old username “rabbit@V …”

$ /opt/local/sbin/rabbitmqctl status
Status of node rabbit@V …
{badrpc,nodedown}
…done.

My install of rabbitmq is though mac ports. Deleting the rabbit directory and contents within /opt/local/var/lib/rabbitmq/mnesia/rabbit/ did the trick for me.

By: Alexandre

Alexandre — Fri, 19 Jun 2009 13:33:39 +0000

>Are you sure broker process is running as user rabbitmq?

the ps axu | grep rabbit show that process user is rabbitmq

By: Dmitriy

Dmitriy — Thu, 18 Jun 2009 15:16:45 +0000

~root/.erlang.cookie should not be relevant to this. When you start rabbitmqctl as root, it does “su” to user rabbitmq and hence uses ~rabbitmq/.erlang.cookie.

Because net_adm commands do not hang, your epmd setup is OK. Which leaves out possibilities of user mix up or cookie mix up.

Are you sure broker process is running as user rabbitmq?

By: Alexandre

Alexandre — Thu, 18 Jun 2009 15:10:47 +0000

Hi Dmitriy,

I install the RB-MQ on the MacOs and d’nt have problem. But I install RB-MQ on the FreeBSD 7 (64-bit) , I can’t start the rabbitmqctl.

the net_adm:localhost() write DNS server name
the net_adm:names() write {ok,[{"rabbit",1088}]}

the chmod file ~root/.erlang.cookie is x400 (20 bytes)

how I can to start rabbitmqctl?

By: Dmitriy

Dmitriy — Sun, 17 May 2009 04:26:16 +0000

Tim,

If net_adm:names() does not hang and rabbit appears in the list, it means the problem is not related to epmd and host addressing.

- Dmitriy

By: Timothy Perrett

Timothy Perrett — Sat, 16 May 2009 22:01:49 +0000

Hi Dmitriy, great article. However, one thing that is not clear to me is the significance of net_adm:names(). ? I am running the broker as “rabbitmq” user and then try to run rabbitmqctl and I still get the {badrpc,nodedown} error.

If both are running as the same user, how on earth am i still seeing this?

Cheers, Tim

By: Dmitriy

Dmitriy — Wed, 04 Mar 2009 17:05:38 +0000

The issue is that when you run “rabbitmqctl status” as root, it tries to su to user rabbitmq (take a look inside rabbitmqctl). And since your broker is running as root, user rabbitmq can’t get its cookie (stored in ~root/.erlang.cookie) and so can’t talk to the broker node.

By: riteshrathi

riteshrathi — Wed, 04 Mar 2009 16:53:56 +0000

“Are you running broker as user rabbitmq and rabbitmqctl as root or rabbitmq? If not, please stop and fix this. This is not a requirement per se, but this represents canonical installation of rabbitmq broker. You can certainly hack your scripts to work around this requirement, but you are on your own if you do.”

Donot understand this point of yours. I have installed the broker as root and also trying to get the status as root. I am getting this error.

net_adm:names(). returns {ok,[{"rabbit",35217},{"foo",57135}]}

Not able to identify what is the problem. Can you please help ?