[rabbitmq-discuss] RabbitMQ server 3.1.3: "badmatch, {error, not_found}" (server down)

[Badjatya, Nikunj]

Hello All,

Any thoughts on this?

Thanks.


-----Original Message-----
From: Badjatya, Nikunj 
Sent: Wednesday, June 04, 2014 8:52 PM
To: 'Matthias Radestock'; 'Discussions about RabbitMQ'
Subject: RE: [rabbitmq-discuss] RabbitMQ server 3.1.3: "badmatch, {error, not_found}" (server down)

Thank you all for quick replies.
Well this issue was not reproducible and we hit this only once.

I didn’t quite understand the reason given in http://markmail.org/thread/26j56abreqwd32fq#query:+page:1+mid:2j2la4yehcxferjy+state:results link.

Can you please explain it in simpler way?

I am not deleting node as part of any operation. Here are the operations which I am doing currently using Pika python library:

1. Create user using rabbitmqctl
2. Connect to localhost using BlockingConnection 3. get channel 4. create exchange if not done already 5. publish using basic_publish 6. Close connection 6. Delete user using rabbitmqctl


Thanks
Nikunj


-----Original Message-----
From: Matthias Radestock [mailto:matthias at rabbitmq.com]
Sent: Tuesday, June 03, 2014 4:55 PM
To: Discussions about RabbitMQ
Cc: Badjatya, Nikunj
Subject: Re: [rabbitmq-discuss] RabbitMQ server 3.1.3: "badmatch, {error, not_found}" (server down)

On 03/06/14 11:41, Michael Klishin wrote:
> On 3 June 2014 at 14:15:52, Badjatya, Nikunj (nikunj.badjatya at emc.com) wrote:
>>>
>> Stack trace:
>> [{rabbit_binding,recover_semi_durable_route,3,[]},
>> {rabbit_binding,'-recover/2-lc$^0/1-0-',3,[]},
>> {rabbit_binding,recover,2,[]},
>> {rabbit,recover,0,[]},
>> {rabbit,'-run_boot_step/1-lc$^1/1-1-',1,[]},
>> {rabbit,run_boot_step,1,[]},
>> {rabbit,'-start/2-lc$^0/1-0-',1,[]},
>> {rabbit,start,2,[]}]
>
> See http://markmail.org/thread/26j56abreqwd32fq and http://markmail.org/thread/ntgfmmmnfrhjodtj.
>
> This is a known bug (#25783) which is not resolved yet.

Actually, there is a bug with the above signature that we fixed in 3.2.0

25822 prevent crash at startup when starting a clustered node hosting a
       durable non-HA queue which had been bound to a transient exchange which
       was deleted when the node was down (since 2.5.0)

Does that at all sound like what might be happening?

If not then, as Simon says, please send him a copy of the mnesia dir off-list.

Matthias.