What I found is that the uptime value was not reset for the node-3 after it was rebooted, which is wrong:
node-4 lrmd: before node-3 reset 2015-12-29T13:34:44.242420+00:00 info: INFO: p_rabbitmq-server: get_monitor(): comparing our uptime (4490) with node-9.domain.tld (4488) 2015-12-29T13:34:44.317439+00:00 info: INFO: p_rabbitmq-server: get_monitor(): comparing our uptime (4490) with node-3.domain.tld (7142) after node-3 reset 2015-12-29T13:38:23.253014+00:00 info: INFO: p_rabbitmq-server: get_monitor(): comparing our uptime (4709) with node-9.domain.tld (4707) 2015-12-29T13:38:23.359804+00:00 info: INFO: p_rabbitmq-server: get_monitor(): comparing our uptime (4709) with node-3.domain.tld (7361)
What I found is that the uptime value was not reset for the node-3 after it was rebooted, which is wrong:
node-4 lrmd: 29T13:34: 44.242420+ 00:00 info: INFO: p_rabbitmq-server: get_monitor(): comparing our uptime (4490) with node-9.domain.tld (4488) 29T13:34: 44.317439+ 00:00 info: INFO: p_rabbitmq-server: get_monitor(): comparing our uptime (4490) with node-3.domain.tld (7142) 29T13:38: 23.253014+ 00:00 info: INFO: p_rabbitmq-server: get_monitor(): comparing our uptime (4709) with node-9.domain.tld (4707) 29T13:38: 23.359804+ 00:00 info: INFO: p_rabbitmq-server: get_monitor(): comparing our uptime (4709) with node-3.domain.tld (7361)
before node-3 reset
2015-12-
2015-12-
after node-3 reset
2015-12-
2015-12-