ubuntu@hostname:~$ sudo service rabbitmq-server start
* Starting message broker rabbitmq-server [ OK ]
ubuntu@hostname:~$ sudo service rabbitmq-server stop
* Stopping message broker rabbitmq-server * message broker already stopped
[ OK ]
ubuntu@hostname:~$ sudo service rabbitmq-server status
Status of node 'rabbit@hostname' ...
Error: unable to connect to node 'rabbit@hostname': nodedown
DIAGNOSTICS
===========
attempted to contact: ['rabbit@hostname']
rabbit@hostname:
* connected to epmd (port 4369) on hostname
* epmd reports: node 'rabbit' not running at all
no other nodes on hostname
* suggestion: start the node
current node details:
- node name: 'rabbitmq-cli-19082@hostname'
- home dir: /var/lib/rabbitmq
- cookie hash: Zoi/1N8mjGUsELj8Z7yzoA==
ubuntu@hostname:~$
I tried to reset it using sudo rabbitmqctl reset
and sudo rabbitmqctl force_reset
both did not work.
remove /var/log/rabbitmq/* and start it back
from : https://groups.google.com/forum/#!topic/rabbitmq-users/w0aJNmfz1N8
In my case it was a problem with the service not started properly.
After trying the accepted solution I just did an additional
and it worked. After that, the second node connected without problems again to the other node.
empd report to my knowledge is a part of OTP(Erlang) peer recognition for rabbitmq, installed as a dependency while installing rabbitmq. You can check the erl_crash.dump file to check the reason for the crash and act accordingly.
If you are not able to make anything out of the crash report, you can simply change the rabbitmq.config to default value. I got my rabbitmq like this. You will find the default settings in rabbitmq.congif.example file. Once you are done with this, restart the rabbitmq server and it should work.
It was selinux in my case, have a look what is in rabbit log file /var/log/rabbirmq/(nodename@host).log if it is anything about ports then it might be selinux
You might need to set the acces rights correctly, using
chmod 644 /etc/rabbitmq/enabled_plugins
and then start the service again withservice rabbitmq-server restart