On a three node cluster, one ec2 machine reboots unexpectedly, and when it
starts up again RabbitMQ fails to start. I've put all logs here:

When the troubled node is restarted manually again it's unable to join,
stopping at "adding mirrors", staying there forever.

The other nodes now start to behave weird too, new queues can't be declared,
but existing queues seems to continue deliver messages. They also can't
respond to "rabbitmqctl status", or /api/overview. I'm forced to stop them
with "kill -9". Only when all nodes are stopped the cluster can be brought
up again normally.

View this message in context: http://rabbitmq.1065348.n5.nabble.com/Node-crash-then-cluster-collapse-tp27206.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 3 | next ›
Discussion Overview
grouprabbitmq-discuss @
postedJun 5, '13 at 12:56p
activeJun 6, '13 at 3:28p

2 users in discussion

Carlhoerberg: 2 posts Tim Watson: 1 post



site design / logo © 2018 Grokbase