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

Matthias Radestock matthias at rabbitmq.com
Tue Jun 3 12:24:40 BST 2014


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.


More information about the rabbitmq-discuss mailing list