Comment 5 for bug 1396946

The case could be as well identified by the following loop in the logs /var/log/remote/$affected_node/rabbitmq-server.log:

2014-12-04T14:23:25.387054+00:00 info: INFO: p_rabbitmq-server: get_monitor(): get_monitor function ready to return 0
2014-12-04T14:23:55.502922+00:00 info: INFO: p_rabbitmq-server: get_monitor(): get_status() returns 0.
2014-12-04T14:23:55.505885+00:00 info: INFO: p_rabbitmq-server: get_monitor(): also checking if we are master.
2014-12-04T14:23:55.609653+00:00 info: INFO: p_rabbitmq-server: get_monitor(): master attribute is (null)
2014-12-04T14:23:55.709681+00:00 info: INFO: p_rabbitmq-server: get_monitor(): checking if rabbit app is running
2014-12-04T14:23:55.712210+00:00 info: INFO: p_rabbitmq-server: get_monitor(): preparing to update master score for node
2014-12-04T14:23:55.733834+00:00 info: INFO: p_rabbitmq-server: get_monitor(): comparing our uptime (0) with node-1 (2739)

it repeats for ever and there is no more messages in the log about 'healthy' cluster