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

[Chris]

Matthias and Team,

Many, many thanks for your help in this matter.  We'll proceed with your
recommended approach.  We will also probably stop doing upgrades on running
clusters.  It seems it might be safer to do the full procedure (bringing
down the whole cluster for the upgrade).

If you happen to find the cause of this bug at some point, of course I
would be interested to know (especially if you fix it).

Thanks again,
Chris


On Tue, Sep 24, 2013 at 8:00 AM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> Chris,
>
> (putting list back on cc)
>
>
> On 23/09/13 21:42, Chris wrote:
>
>> Thank you very much for taking a look at these logs.  It is a strange
>> bug for sure!  I guess I have two goals, really:
>>
>>   * To get the customer back up and running in the least disruptive way
>>   * To help you guys understand what happened since I know it's no fun
>>
>>     to have mystery bugs in your product. ;-)
>>
>> Regarding #1, if there is not a minimally disruptive way, I am assuming
>> I will need to reset all nodes and rebuild the cluster.
>>
>
> You should be able to recover the 'not found' bindings by a) recreating
> the queues (as you already have) and then b) stopping the entire cluster
> (i.e. no node must be left running) and restarting it.
>
>
>  Regarding #2, if you need anything else from me, please let me know!
>>
>
> There is no smoking gun in the logs, so the likely source of the problem
> is some edge case error in the mirroring and/or recovery logic. That may
> take us a while to track down. I don't think there's any other info we need
> from your running cluster. Thanks for reporting this issue.
>
>
> Regards,
>
> Matthias.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130924/0f3d1bf9/attachment.htm>