[rabbitmq-discuss] Can't Bind After Upgrading from 3.1.1 to 3.1.5
Matthias Radestock
matthias at rabbitmq.com
Fri Sep 20 21:27:50 BST 2013
Chris,
On 20/09/13 21:01, Chris wrote:
> According to "rabbitmqctl cluster_status" and the management web
> console, all 5 nodes were up in the cluster (with no partitions).
But was that *always* the case? Would be good to see the logs all the
way from the time of the upgrade.
> Still, I would think that successfully deleting and creating the
> queue in the management console would indicate the queue should be
> alive and on an online node.
Yes, that should be the case.
> If this is in fact a bug, is there anything you can recommend to get
> it into a better state?
Hard to know without understanding what the problem is. Is this
reproducible at all? e.g. do you have a queue *now* that is suffering
from this behaviour?
Matthias.
More information about the rabbitmq-discuss
mailing list