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

The Rabbitmq server does not start, stating that it is 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 it looks like rabbitmqctl is thinking differently:

 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 members?

+45
rabbitmq
Jan 05 2018-12-12T00:
source share
7 answers

The rabbitmq server was running somewhere, but you just couldn't connect to it.

One of the following will mention rabbits:

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

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

+50
Jan 05 '12 at 5:14
source share

I had the same problem, then I realized that I did not issue the correct command.

 ./rabbitmqctl stop 

this works every time, although it also reduces erlang runtime. also remember where your configuration file is located.

+27
Jun 15 2018-12-12T00:
source share

This problem can be caused by two problems:

  • Rabbit is already running on the server. If so, use the answer you found about killing the current process (ps aux | grep rabbit | grep -v grep)
  • You changed the IP address of your device, but did not change the / etc / hosts file to display the new device IP address.

The most common problems are the first, but it’s harder to find the second (especially if you have a rabbit running on another machine. If the rabbit is installed on another machine, it will look at the old IP address and see that another machine is already running rabbitmq and gives the same mistake for you, it made me sad in the past.

+12
Jun 22 '13 at 6:16
source share

I had the same @Win 7 error, but the solutions above did not work for me, which was decided to uninstall and reinstall the service. Using the console with administrator rights:

rabbitmq-service remove

installing rabbitmq-service

Hope this helps someone else too.

+3
May 12 '16 at 17:44
source share

In my case under Ubuntu 11.10 this helped

 #rabbitmqctl cluster MASTER SLAVE #rabbitmqctl start_app 

before i always get this error message ...

+1
May 17 '12 at 9:59 a.m.
source share

Using the admin console, in Win 2012R2 ver 3.5.5 rabbit, it started working by uninstalling and installing, and then restarting the rabbitmq server then ctr-c to shut down, then I was able to use the Windows services console and start the rabbitMq service.

0
Apr 7 '17 at 14:20
source share

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

0
Nov 17 '17 at 20:04
source share



All Articles