Replies: 3 comments
-
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :( |
Beta Was this translation helpful? Give feedback.
-
We haven't seen this in a few years but the trace is specific enough.
|
Beta Was this translation helpful? Give feedback.
-
It's worth mentioning that the node likely is running but CLI tools run into an error because of this failing/effectively missing I/O process that leads them to believe that RabbitMQ must have been stopped on this node. |
Beta Was this translation helpful? Give feedback.
-
I started a cluster of three nodes yesterday. The rabbitmqctl commands were able to display the status of the cluster as well as stopping and starting the nodes.
Today, when I run the command
rabbitmqctl cluster_status
I got the following error:However, in the management dashboard, all the nodes appear to be running and clients are able to send messages to the server.
Still, I run the command
rabbitmqctl start_app
and it appears to start the node according to the logs but with some errors. Therabbitmqctl cluster_status
doesn't recognize the app running in the target node. Also,rabbitmqctl stop_app
doesn't stop any of the nodes that appear to be running in the management console.The relevant log excerpt seems to be: (full log below)
Full log
And this is from the
crash.log
To be able to use
rabbitmqctl
I had to kill the processes and start the servers again but this is not ideal.Thank you.
Beta Was this translation helpful? Give feedback.
All reactions