[rabbitmq-discuss] Can't Bind After Upgrading from 3.1.1 to 3.1.5

Fri Sep 20 22:23:24 BST 2013

Chris,

On 20/09/13 22:00, Chris wrote:
> I can try to get the logs.  Of course, during the upgrade nodes went up
> and down...  So there could have been a time when the nodes the queue
> was on were both down.  But this continued even after all nodes were
> back up and the queue was recreated.

Right. I want to check the logs for anything unusual.

> It is very reproducible now on this specific customer system (we haven't
> yet resolved it there since I was hoping for an option that doesn't
> include clearing mnesia or resetting the nodes).  So, yes, I can make
> the binding fail all I want on that system.

In which case please post the output of 'rabbitmqctl report' from one of 
the nodes, and a screenshot of the management UI when you get the 
NOT_FOUND error.

Regards,

Matthias.