[rabbitmq-discuss] queue_declare returning a (50, 10) NOT_FOUND....

[Nigel Benns]

Hey Guys,

I'm having this issue as well.
I have never had clustering enabled, but it appears that I was setting 
"autoDelete=true", "exclusive=true" and durable="true".
Since then have changed autoDelete=false.

I'm connecting through node-amqp.

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.
Could the autoDelete logic have half succeeded?
Also I have a erl_crash.dump file, but I don't get much from it myself.

here is the output of status:

Status of node rabbit at beast ...
[{pid,531},
 {running_applications,
     [{rabbitmq_jsonrpc_channel_examples,"rabbit_jsonrpc_channel_examples",
          "2.6.1"},
      {rabbitmq_management_visualiser,"RabbitMQ Visualiser","2.6.1"},
      {rabbitmq_management,"RabbitMQ Management Console","2.6.1"},
      {rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.6.1"},
      {webmachine,"webmachine","1.7.0-rmq2.6.1-hg0c4b60a"},
      {amqp_client,"RabbitMQ AMQP Client","2.6.1"},
      {rabbitmq_management_agent,"RabbitMQ Management Agent","2.6.1"},
      {mochiweb,"MochiMedia Web Server","1.3-rmq2.6.1-git9a53dbd"},
      {inets,"INETS  CXC 138 49","5.7.1"},
      {rabbitmq_stomp,"Embedded Rabbit Stomp Adapter","2.6.1"},
      {rabbit,"RabbitMQ","2.6.1"},
      {mnesia,"MNESIA  CXC 138 12","4.5"},
      {os_mon,"CPO  CXC 138 46","2.2.7"},
      {sasl,"SASL  CXC 138 11","2.1.10"},
      {stdlib,"ERTS  CXC 138 10","1.17.5"},
      {kernel,"ERTS  CXC 138 10","2.14.5"}]},
 {os,{unix,linux}},
 {erlang_version,
     "Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:2:2] [rq:2] 
[async-threads:30] [kernel-poll:true]\n"},
 {memory,
     [{total,30854664},
      {processes,11967824},
      {processes_used,11953424},
      {system,18886840},
      {atom,1348001},
      {atom_used,1325858},
      {binary,48664},
      {code,14479935},
      {ets,1217440}]}]
...done.

On Wednesday, 29 September 2010 18:56:53 UTC-4, Nicolás César wrote:
>
> Hi i'm getting a
>
> (404, u"NOT_FOUND - no queue 'xxx in vhost '/'", (50, 10), 
> 'Channel.queue_declare') 
>
> doing a queque_declare, reading from my own thread time ago:
>
> http://groups.google.com/group/rabbitmq-discuss/browse_thread/thread/2d925b0bbaed7f86?pli=1
>
>
> Simon MacMullen replied:
>
> ISTR the only way you can get a not-found when declaring a queue is in a 
> clustering situation, if the queue exists on a node which is not 
> running. Does that sound like it could be a possibility? 
>
> Cheers, Simon 
> but I have no cluster situation:
>
> #/usr/sbin/rabbitmqctl status
> Status of node rabbit at sendsorium ...
> [{running_applications,[{rabbit,"RabbitMQ","1.8.1"},
>                         {mnesia,"MNESIA  CXC 138 12","4.4.14"},
>                         {os_mon,"CPO  CXC 138 46","2.2.5"},
>                         {sasl,"SASL  CXC 138 11","2.1.9.2"},
>                         {stdlib,"ERTS  CXC 138 10","1.17"},
>                         {kernel,"ERTS  CXC 138 10","2.14"}]},
>  {nodes,[{disc,[rabbit at sendsorium]}]},
>  {running_nodes,[rabbit at sendsorium]}]
> ...done.
>
> Thanks in advance!
>
>
> 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.
>
>
> Nico César
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120319/823c9e79/attachment.htm>