[rabbitmq-discuss] Return of 'getting started, broker runs; can't get status'
pauljones23 at gmail.com
Tue Sep 22 10:59:12 BST 2009
Just so we can understand your setup, how are you trying to setup the users
for rabbit? Did you do the build as a rabbitmq user, or ...?
One of the most likely causes of the nodedown tends to be cookie mismatches,
which can be hard to definitively check. In both the rabbitmq-server and
rabbitmqctl scripts, can you please add the follow line somewhere within the
command line flags (perhaps after the -sname):
-eval 'io:format("~p~n", [init:get_argument(home)])'
This will print (badly formatted I'm afraid) the home directory that erlang
is seeing, and subsequently allows you to determine that the home
directories are the same. If they are, it could also be worth adding:
-eval 'io:format("~p~n", [erlang:get_cookie()])'
This will dump the value of the erlang cookie. Generally, the Erlang cookie
should be considered somewhat private, so I'll leave it up to you whether
you want to post it to the mailing list. Simply providing detail on whether
they are the same is enough.
On Tue, Sep 22, 2009 at 9:58 AM, J Aaron Farr <farra at apache.org> wrote:
> On Tue 22 Sep 2009 16:43, Paul Jones <pauljones23 at gmail.com> wrote:
> > Is rabbit running as root or rabbitmq? If you're running rabbit as
> > then you may need to add "-U rabbitmq" to the sudo command to ensure that
> > rabbitmqctl is running as the same user.
> I've tried both combinations, as root and as rabbitmq. I've checked to
> ensure both processes are run as the exact same user. Still no dice.
> I've also made sure every rabbitmq directory is owned by rabbitmq.
> `net_adm:localhost().` returns 'gandalf.local' which is the name of the
> local computer. I've even added a line in /etc/hosts for gandalf.local
> for 127.0.0.1.
> I'm really stumped here.
> J. Aaron Farr
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss