[rabbitmq-discuss] getting started, broker runs; can't get status

Sat Jan 31 19:39:47 GMT 2009

Dave Farkas wrote:

> Here is what i happens when i run rabbitmqctl out of /user/sbin:
> 
> [root at db1 sbin]# ./rabbitmqctl status
> Status of node rabbit at db1 ...
> {badrpc,nodedown}
> ...done.
> 
> Is there anything else I should try?

The following may help us track down the problem:

1) stop rabbit (just kill the process if everything else fails)

2) kill the 'epmd' process

3) start epmd in non-daemon and debugging mode and capture its logs - 
you can do that as any user:
   epmd -d > /tmp/epmd.log 2>&1 &

4) start the rabbitmq server in the normal way, e.g.
   sudo /etc/init.d/rabbitmq-server start

5) run the rabbitmqctl command in the normal way, e.g.
   sudo rabbitmqctl status

6) stop epmd by killing the process

7) send me the /tmp/epmd.log file

Here's what the log file looks for me when I do the above:

epmd: Sat Jan 31 19:30:19 2009: epmd running - daemon = 0
epmd: Sat Jan 31 19:30:32 2009: ** got ALIVE2_REQ
epmd: Sat Jan 31 19:30:32 2009: registering 'rabbitmq_multi21852:3', 
port 40125
epmd: Sat Jan 31 19:30:32 2009: type 77 proto 0 highvsn 5 lowvsn 5
epmd: Sat Jan 31 19:30:32 2009: ** sent ALIVE2_RESP for 
"rabbitmq_multi21852"
epmd: Sat Jan 31 19:30:32 2009: ** got PORT2_REQ
epmd: Sat Jan 31 19:30:32 2009: ** sent PORT2_RESP (error) for "rabbit"
epmd: Sat Jan 31 19:30:32 2009: ** got PORT2_REQ
epmd: Sat Jan 31 19:30:32 2009: ** sent PORT2_RESP (error) for "rabbit"
epmd: Sat Jan 31 19:30:32 2009: ** got ALIVE2_REQ
epmd: Sat Jan 31 19:30:32 2009: registering 'rabbit:3', port 45735
epmd: Sat Jan 31 19:30:32 2009: type 77 proto 0 highvsn 5 lowvsn 5
epmd: Sat Jan 31 19:30:32 2009: ** sent ALIVE2_RESP for "rabbit"
epmd: Sat Jan 31 19:30:33 2009: ** got PORT2_REQ
epmd: Sat Jan 31 19:30:33 2009: ** sent PORT2_RESP (ok) for "rabbit"
epmd: Sat Jan 31 19:30:33 2009: unregistering 'rabbitmq_multi21852:3', 
port 40125
epmd: Sat Jan 31 19:30:48 2009: ** got ALIVE2_REQ
epmd: Sat Jan 31 19:30:48 2009: registering 'rabbitmqctl21934:1', port 59932
epmd: Sat Jan 31 19:30:48 2009: type 77 proto 0 highvsn 5 lowvsn 5
epmd: Sat Jan 31 19:30:48 2009: ** sent ALIVE2_RESP for "rabbitmqctl21934"
epmd: Sat Jan 31 19:30:48 2009: ** got PORT2_REQ
epmd: Sat Jan 31 19:30:48 2009: ** sent PORT2_RESP (ok) for "rabbit"
epmd: Sat Jan 31 19:30:48 2009: unregistering 'rabbitmqctl21934:1', port 
59932

I suspect your log file will look substantially different, unless the 
above steps happen to coincidentally "fix" the problem.

Regards,

Matthias.