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

[Chris]

Hi Matthias,

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.

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.  I cannot, however, get the bug to
reproduce on any other systems.

Thanks again,
Chris


On Fri, Sep 20, 2013 at 4:27 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130920/a3214c9d/attachment.htm>