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

[Chris]

Hi Matthias,

According to "rabbitmqctl cluster_status" and the management web console,
all 5 nodes were up in the cluster (with no partitions).  In addition, I
could see the queue in the web management console-- and successfully
deleted and re-created the queue too.  I also could successfully create
other bindings against the same queue and exchange.

I did not try "rabbitmqctl list_qeueus" (and don't have access to the
system right now to try it).  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.

If this is in fact a bug, is there anything you can recommend to get it
into a better state?

-Chris




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

> Chris,
>
>
> On 20/09/13 18:14, Chris wrote:
>
>> After upgrading a customer site from RabbitMQ 3.1.1 to 3.1.5 (on RHEL
>> 6.2), we had a few durable queues that did not seem to be working
>> correctly (they weren't receiving any messages).  It should be noted
>> that this is a cluster of 5 servers with queue mirroring set to exactly
>> 2 nodes.
>>
>> During troubleshooting, we deleted and recreated the queues.  After
>> creating the queues, we attempted to rebind them to the exchange (in the
>> web management GUI), but this always failed.
>>
>> [In the following example, names have been changed to protect the
>> innocent].  After attempting to bind durable mirrored 'my.queue' to
>> durable direct exchange 'my.exchange' using routing key 'my.queue' (in
>> vhost 'abc'), we get the following error:
>>
>>     NOT_FOUND - no binding my.queue between exchange 'my.exchange' in
>>     vhost 'abc' and queue 'my.queue' in vhost 'abc'
>>
>
> That happens when the binding in question exists but the 'home' node of
> the (durable) queue is not alive. In case of a mirrored queue that would
> imply that all mirrors are down. Essentially both the queue and associated
> bindings are in a limbo state at that point - they neither exist nor do
> they not exist.
>
> So when you see the above error, please check whether the queue you are
> binding actually exists, i.e. shows up in 'rabbitmqctl list_queues'. If it
> does not then you are seeing normal behaviour. Otherwise there's a bug.
>
> Regards,
>
> Matthias.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130920/f04b2fb2/attachment.htm>