Hey Guys,<br><br>I'm having this issue as well.<br>I have never had clustering enabled, but it appears that I was setting "autoDelete=true", "exclusive=true" and durable="true".<br>Since then have changed autoDelete=false.<br><br>I'm connecting through node-amqp.<br><br>rabbitmqctl doesn't appear to know anything about the queue, however I see the queue listed in rabbit_durable_queue.DCD and rabbit_durable_route.DCD.<br>Could the autoDelete logic have half succeeded?<br>Also I have a erl_crash.dump file, but I don't get much from it myself.<br><br>here is the output of status:<br><br>Status of node rabbit@beast ...<br>[{pid,531},<br> {running_applications,<br> [{rabbitmq_jsonrpc_channel_examples,"rabbit_jsonrpc_channel_examples",<br> "2.6.1"},<br> {rabbitmq_management_visualiser,"RabbitMQ Visualiser","2.6.1"},<br> {rabbitmq_management,"RabbitMQ Management Console","2.6.1"},<br> {rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.6.1"},<br> {webmachine,"webmachine","1.7.0-rmq2.6.1-hg0c4b60a"},<br> {amqp_client,"RabbitMQ AMQP Client","2.6.1"},<br> {rabbitmq_management_agent,"RabbitMQ Management Agent","2.6.1"},<br> {mochiweb,"MochiMedia Web Server","1.3-rmq2.6.1-git9a53dbd"},<br> {inets,"INETS CXC 138 49","5.7.1"},<br> {rabbitmq_stomp,"Embedded Rabbit Stomp Adapter","2.6.1"},<br> {rabbit,"RabbitMQ","2.6.1"},<br> {mnesia,"MNESIA CXC 138 12","4.5"},<br> {os_mon,"CPO CXC 138 46","2.2.7"},<br> {sasl,"SASL CXC 138 11","2.1.10"},<br> {stdlib,"ERTS CXC 138 10","1.17.5"},<br> {kernel,"ERTS CXC 138 10","2.14.5"}]},<br> {os,{unix,linux}},<br> {erlang_version,<br> "Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:2:2] [rq:2] [async-threads:30] [kernel-poll:true]\n"},<br> {memory,<br> [{total,30854664},<br> {processes,11967824},<br> {processes_used,11953424},<br> {system,18886840},<br> {atom,1348001},<br> {atom_used,1325858},<br> {binary,48664},<br> {code,14479935},<br> {ets,1217440}]}]<br>...done.<br><br>On Wednesday, 29 September 2010 18:56:53 UTC-4, Nicolás César wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><font>Hi i'm getting a<br><br>(404, u"NOT_FOUND - no queue 'xxx in vhost '/'", (50, 10), 'Channel.queue_declare') </font><br><br>doing a queque_declare, reading from my own thread time ago:<br>
<a href="http://groups.google.com/group/rabbitmq-discuss/browse_thread/thread/2d925b0bbaed7f86?pli=1" target="_blank">http://groups.google.com/<wbr>group/rabbitmq-discuss/browse_<wbr>thread/thread/<wbr>2d925b0bbaed7f86?pli=1</a><br><br><br>Simon MacMullen replied:<br>
<p><font>ISTR the only way you can get a not-found when declaring a queue is in a <br> clustering situation, if the queue exists on a node which is not <br> running. Does that sound like it could be a possibility? <br>
</font></p><p><font>Cheers, Simon </font></p>but I have no cluster situation:<br><br>#/usr/sbin/rabbitmqctl status<br>Status of node rabbit@sendsorium ...<br>[{running_applications,[{<wbr>rabbit,"RabbitMQ","1.8.1"},<br>
{mnesia,"MNESIA CXC 138 12","4.4.14"},<br> {os_mon,"CPO CXC 138 46","2.2.5"},<br> {sasl,"SASL CXC 138 11","2.1.9.2"},<br>
{stdlib,"ERTS CXC 138 10","1.17"},<br> {kernel,"ERTS CXC 138 10","2.14"}]},<br> {nodes,[{disc,[rabbit@<wbr>sendsorium]}]},<br> {running_nodes,[rabbit@<wbr>sendsorium]}]<br>
...done.<br><br>Thanks in advance!<br><br><br>BTW. my last issue with rabbit not starting were bizarre virtualization problems like not ping'ing 127.0.0.1 my apologies for the noise to the list.<br><br><br clear="all">
Nico César<br>
</blockquote>