Skip to content

Node fails to start with error access to vhost '/' refused for user 'XXXX': vhost '/' is down #10052

Discussion options

You must be logged in to vote

I recall discussing this with another core team member and our conclusion was the following: if the mounted volume is not yet ready for writes by the time the node boots, it will fail to seed the data and the virtual host then will fail to stop.

This is pretty clearly hinted at by one of the function names: rabbit_variable_queue:do_start_msg_store/4.

We have never seen this behavior outside of Kubernetes, and RabbitMQ nodes do not do anything creative when it comes to initializing the schema data store or the CQ message store. So there is nothing to "fix once and for all" in RabbitMQ.

A while ago we have considered adding optional delays before and after the node boots, for very different…

Replies: 3 comments 2 replies

Comment options

You must be logged in to vote
2 replies
@ravisingh-adeptia
Comment options

@michaelklishin
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by michaelklishin
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants