[rabbitmq-discuss] Error in start_app through rabbitmqctl..
Simon MacMullen
simon at rabbitmq.com
Tue Oct 15 12:09:42 BST 2013
On 14/10/13 17:07, k.madnani84 wrote:
> =INFO REPORT==== 14-Oct-2013::08:13:16 ===
> Error description:
> {badmatch,{error,not_found}}
>
> 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,[]}]
Hi.
This is a bug in biding recovery. It's triggered when you bind a
transient exchange to an unmirrored durable queue, then stop the node
the queue is on, then delete the exchange. It then becomes impossible to
start the stopped node again.
We'll fix this, hopefully in the next release. As a workaround, you can
stop the entire cluster and start it again.
Cheers, Simon
--
Simon MacMullen
RabbitMQ, Pivotal
More information about the rabbitmq-discuss
mailing list