Open gevgev opened 6 years ago
Couple of more folder contents and file content:
root@secondary:~# ll /var/lib/rabbitmq/mnesia/
total 16
drwxr-x--- 4 rabbitmq rabbitmq 4096 Sep 22 16:04 ./
drwxr-xr-x 3 rabbitmq rabbitmq 4096 Mar 24 2015 ../
drwxr-xr-x 4 rabbitmq rabbitmq 4096 Sep 22 16:04 rabbit@vagrant-ubuntu-trusty-64/
drwxr-xr-x 22 rabbitmq rabbitmq 4096 Sep 22 16:04 rabbit@vagrant-ubuntu-trusty-64-plugins-expand/
And the content of cluster_nodes.config file:
root@secondary:~# cat /var/lib/rabbitmq/mnesia/rabbit@vagrant-ubuntu-trusty-64/cluster_nodes.config
{['rabbit@vagrant-ubuntu-trusty-64'],['rabbit@vagrant-ubuntu-trusty-64']}.
root@secondary:~#
Did this issue resolve? I have this issue as well today.
Resolved this as
ps -ef | grep rabbitmq
ps -ef | grep rabbitmq | grep -v grep | awk '{print $2}' | xargs kill -9
rabbitmq-server
Trying to bring the secondary node up, per instructions, running 'vagrant up secondary' command, getting the following error:
Looks like the node name is not configured properly, as here is what I see if I ssh in the secondary node using
vagrant ssh secondary
:Here is how the /var/log/rabbitmq/ folder's content looks like:
I was expecting the see the log file names to be 'rabbit@secondary.log' etc. And here are the top 10 lines from the log file, which shows the node name (in bold below):
This command also confirms the node name mismatch:
Also attempted to restart the service:
Thanks.