<font class="fixed_width">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">http://groups.google.com/group/rabbitmq-discuss/browse_thread/thread/2d925b0bbaed7f86?pli=1</a><br><br><br>Simon MacMullen replied:<br>
<p><font class="fixed_width">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 class="fixed_width">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,[{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@sendsorium]}]},<br> {running_nodes,[rabbit@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>