[rabbitmq-discuss] Someone else with a nodedown error

Tim Watson tim at rabbitmq.com
Fri May 17 14:32:52 BST 2013


On 17 May 2013, at 13:45, Eric Berg wrote:

> Thanks for your response Tim. If you would like SSH access to these boxes let me know, we can work something out privately. Thanks!

Ok, though first of all I'd like to know if you supply logs for the nodes in question? A private drop box would be fine.

> Update from yesterday:
> It looks like 2 of the 4 nodes in our cluster have finally shut down, all channels are now gone. Another node in the cluster hangs on
> > sudo rabbitmqctl status
> and the final node in the cluster appears to be running just fine. It however sees the unresponsive node in the cluster status as a running node, as does the web UI.

Right, so we've still got an unresponsive node. Do you have any mirrored queues, and if so, what synchronisation and/or recovery policies are you using?

> When you upgraded your cluster, what RabbitMQ version did you upgrade from and to, and did you upgrade Erlang as well and if so, which versions were involved?
> - we upgraded from 3.0.4 to 3.1.0, we did not upgrade Erlang it was/is at version R15B03. We did however install it via RPM with the --nodeps flag because it did not detect the Erlang dependency correctly. We had previously installed Erlang:
> esl-erlang.x86_64    R15B03-2           @erlang-solutions 

Hmn, I suppose it's possible that this re-install went wrong somehow and is causing some of the things below.

> What happens if you start up Erlang by itself, using `erl -sname test` - do you still see all those screwy warnings? 
> All 4 of the nodes can run this without issue as my user, when I sudo su to rabbitmq user I get errors on 2 of the 4 nodes as such:

Well the nodes should always be running as the rabbitmq user, so how're you starting them as your user? That might be at the root of some of these problems, viz the rabbitmq-server (service) should always run as the rabbitmq user and when issuing rabbitmqctl commands and the like, you would normally do `$ sudo rabbitmqctl status` and so on. Log files would definitely help though.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130517/162874d0/attachment.htm>

More information about the rabbitmq-discuss mailing list