RabbitMQ - Statistics database could not be contacted. Message rates and queue lengths will not be shown?

That's not really a message you should even be able to see in 2.6.1. I would be interested to know how you got there.

That's not really a message you should even be able to see in 2.6.1. I would be interested to know how you got there. The management plugin maintains a single in-memory statistics database on one node in the cluster, even if it's installed on several / all nodes.

Prior to 2.6.0 you would see that error if the node hosting the database failed or was removed. But in 2.6.0 we ensured (or I thought we did) that the statistics database would migrate to another node and reconstruct itself if necessary. So this might not be a very good Stack Overflow question as it's looking more like a bug report.Do you see this after a node has failed / been removed or right from the start?

Is mgmt installed on all nodes or just one? Can you send us the logs from the various nodes? Probably better to reply to support@rabbitmq.

Com in fact.

We are seeing this as well with 2.6.1. – TrueWill Nov 9 at 21:35 We've seen this too. I think it happens when you shut down the statistics node, then rabbit fails it over to node-n, but you shut down node-n before the fail-over completes.

– João Bragança Dec 7 at 22:31.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.