"node with name "rabbit" already running", but also "unable to connect to node 'rabbit'"

Question

Rabbitmq server does not start, saying it's already running:

$: rabbitmq-server
Activating RabbitMQ plugins ...
0 plugins activated:

node with name "rabbit" already running on "android-d1af002161676bee"
diagnostics:
- nodes and their ports on android-d1af002161676bee: [{rabbit,52176},
                                                      {rabbitmqprelaunch2254,
                                                       59205}]
- current node: 'rabbitmqprelaunch2254@android-d1af002161676bee'
- current node home dir: /Users/Jordan
- current node cookie hash: ZSx3slRJURGK/nHXDTBRqQ==

But, rabbitmqctl seems to think otherwise:

rabbitmqctl -n rabbit status
Status of node 'rabbit@android-d1af002161676bee' ...
Error: unable to connect to node 'rabbit@android-d1af002161676bee': nodedown
diagnostics:
- nodes and their ports on android-d1af002161676bee: [{rabbit,52176},
                                                      {rabbitmqctl2462,59256}]
- current node: 'rabbitmqctl2462@android-d1af002161676bee'
- current node home dir: /Users/Jordan
- current node cookie hash: ZSx3slRJURGK/nHXDTBRqQ==

Any takers?

score 74 · Accepted Answer · answered Jan 05 '12 at 05:14

74

The rabbitmq server was running somewhere but it just couldn't be connected to.

One of the following will mention something about rabbits:

$: ps aux | grep epmd
$: ps aux | grep erl

Kill the process with kill -9 {pid of rabbitmq process}

answered Jan 05 '12 at 05:14

Jordan Warbelow-Feldstein

10,510
12
48
79

6

NB: `kill -9` is not usually needed, `kill [pid]` works just fine. – Jay Taylor Jun 22 '12 at 23:57
1

Killing the erlang interpreter will cause problems and errors like "unable to connect to node ". – brimble2010 Nov 05 '12 at 17:20
2

Can also do `sudo pkill -9 -f erl` – radtek May 16 '18 at 14:49

score 50 · Answer 2 · answered Jun 15 '12 at 20:04

50

i was having the same problem then I realized I was not issuing the right command.

./rabbitmqctl stop

this works everytime, although it does take down erlang runtime too. also mind where your config file.

answered Jun 15 '12 at 20:04

baskint

692
5
12

1

this is a much more elegant solution than the kill suggested above IMO – Gaston Oct 26 '15 at 19:34
Thanks - to get this to work issue the following command 'rabbitmqctl stop' into command prompt and then issue 'rabbitmq-server' to restart the server. – Simon Nov 12 '15 at 17:29

score 27 · Answer 3 · answered Nov 17 '17 at 20:04

27

I used rabbitmqctl stop and then restarted using rabbitmq-server as root.

answered Nov 17 '17 at 20:04

user7897287

379
3
8

score 20 · Answer 4 · edited Jan 25 '17 at 18:47

This issue can be caused by two issues:

Rabbit is already running on the server. If that is the case, use the answer you found of killing the currently running process (ps aux | grep rabbit | grep -v grep)
You have changed the IP address of your machine but not changed the /etc/hosts file to reflect the new IP address of the machine.

The more common of the issues is the first, but the harder to find is the second (especially if you have rabbit running on the other machine. If rabbit is installed on the other machine it will look at the old IP address and would see another machine already running rabbitmq and give you the same error. This has caused me grief in the past.

Yeah that /etc/hosts gets me every time. So for everyone else, make sure the /etc/hosts file contains the name of your server e.g. "127.0.0.1 server2452 server2452.site.com" — byoungb, Aug 07 '13 at 13:12

score 7 · Answer 5 · answered May 12 '16 at 17:44

7

I was having this same error @ Win 7, but the solutions above did not worked for me, what did solved was to remove and reinstall the service. Using a console with admin rights:

rabbitmq-service remove

rabbitmq-service install

I hope this might help someone else too

answered May 12 '16 at 17:44

Richard

640
7
13

1

`root@48c0c0dafaed:/# rabbitmq-service remove bash: rabbitmq-service: command not found` – basickarl Jan 25 '17 at 18:46
1

@KarlMorrison Your command is from a bash shell. This answer was referring to commands from the Windows command prompt. This answer worked for me on Windows 10. – Jaime Soto Sep 22 '17 at 15:08
1

this should be the best answer – IamMashed Mar 17 '18 at 15:29

score 2 · Answer 6 · answered Sep 25 '18 at 12:35

2

$CD RabbitMQ Server\rabbitmq_server-3.7.8\sbin

rabbitmq-service remove

rabbitmq-service install

Go : windows Services Find : RabbitMQ and Start it

after this Enable plugin :

rabbitmq-plugins enable rabbitmq_management

answered Sep 25 '18 at 12:35

ZURA Tikaradze

279
5
15

score 1 · Answer 7 · answered May 17 '12 at 09:59

1

In my case under Ubuntu 11.10 it helped to

#rabbitmqctl cluster MASTER SLAVE
#rabbitmqctl start_app

before I always got this error message...

answered May 17 '12 at 09:59

patroqueeet

764
1
8
19

score 0 · Answer 8 · answered Apr 07 '17 at 14:20

0

Using admin console, in Win 2012R2 ver 3.5.5 rabbit, got it to work using the remove and install then rabbitmq-server restart then ctr-c to terminate the job, then I was able to use the windows service console and start the rabbitMq service.

answered Apr 07 '17 at 14:20

user2961800

1
2

score -1 · Answer 9 · answered Mar 15 '18 at 13:44

-1

In my case(windows), 1. I just ran the stop service. 2. The started the service.

answered Mar 15 '18 at 13:44

SRI RaMan

11
3

"node with name "rabbit" already running", but also "unable to connect to node 'rabbit'"

9 Answers9

Linked