Hi,<div><br><div class="gmail_quote">On Wed, Feb 15, 2012 at 5:19 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 15/02/12 01:37, Santosh Thammana wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I had some issues with RabbitMQ, and had to restart it. �The issue was<br>
that the queue sizes were remaining constant, despite there being<br>
producers and consumers. �But after restarting, I am unable to create a<br>
few of my queues.<br>
<br>
I am using Pika, and I get the error:<br>
ChannelClosed: Channel.Close(class_id = 50, method_id = 10, reply_code =<br>
404, reply_text = "NOT_FOUND - no queue 'collector.be2' in vhost '/'")<br>
</blockquote>
<br></div>
The only way to get a NOT_FOUND when declaring a queue is if the queue has previously been declared on a cluster node which is currently down. Does that describe your situation?<div class="im"><br></div></blockquote><div>
��</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I get the same error if I then try to delete it.<br>
We noticed that the queue is still bound to the default exchange. �So,<br>
it seems like that's causing the strange behavior. �And I can't delete a<br>
default binding.<br>
</blockquote>
<br></div>
The default binding should not prevent you from declaring the queue.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
�Is there any way to solve this problem without<br>
restarting RabbitMQ? �If I do have to restart RabbitMQ, can I expect it<br>
to be in a proper state? �I noticed that at least one of the queues I<br>
had issues with was declared as durable. �I'm not sure if that impacted<br>
this negatively.<br>
</blockquote>
<br></div>
I think they would all have to be durable.<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br></div><div>We were able to get this to work. �We don't have a cluster - there's just one server. �It seems that after several hours, the queue server's state was fixed. �We were able to create the desired queues. �Thanks for your help!</div>