Comment 3 for bug 1334314

Revision history for this message
Cian O'Driscoll (dricco) wrote :

This is easily reproduced by restarting the seed and running os-refresh-config

Some other notes

root@hLinux:/opt/stack/os-config-refresh# service rabbitmq-server stop
stop: Job has already been stopped: rabbitmq-server

but service is still running

only the following manages to stop rabbit

root@hLinux:/opt/stack/os-config-refresh# /usr/sbin/rabbitmq-server stop
ERROR: node with name "rabbit" already running on "hLinux"

DIAGNOSTICS
===========

nodes in question: [rabbit@hLinux]

hosts, their running nodes and ports:
- hLinux: [{rabbitmqctl2187,57162},
           {rabbit,5535},
           {rabbitmqprelaunch10094,37627}]

current node details:
- node name: rabbitmqprelaunch10094@hLinux
- home dir: /mnt/state/var/lib/rabbitmq
- cookie hash: 4hgbUBSmcVnMIwyP4NbFtg==