Unfortunately, its just been pointed out to me that you are using a non-default vhost which the BQL tool currently can't do. So perhaps it won't be useful in your situation at this point in time. Sorry about that.<br>
<br><div class="gmail_quote">On Thu, Nov 5, 2009 at 3:47 PM, Paul Jones <span dir="ltr"><<a href="mailto:pauljones23@gmail.com">pauljones23@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Owen,<br><br>You've got two options for this. Either you can write a client app to do a queue purge, or you can install the BQL plugin which provides a console that you can execute commands on.<br><br>The page at <a href="http://www.rabbitmq.com/rabbitmq-bql.html#installation" target="_blank">http://www.rabbitmq.com/rabbitmq-bql.html#installation</a> discusses installation of this plugin - once you've done that, you should be able to execute a command such as:<br>
BQL> purge queue celerygraph;<br><br>Thanks,<br><font color="#888888">Paul.</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Thu, Nov 5, 2009 at 2:22 PM, Owen Nelson <span dir="ltr"><<a href="mailto:onelson@ringling.edu" target="_blank">onelson@ringling.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Perhaps this is the culprit?<br>
<br>
rabbitmqctl list_queues -p gmate_test<br>
Listing queues ...<br>
celerygraph 277558<br>
celery 0<br>
...done.<br>
<br>
What's the best way to clear that out? Looking at the man page for<br>
rabbitmqctl, the only thing I see that would potentially do it would be<br>
to reset the node, then rebuild the vhosts/users. Is that the only way?<br>
<div><div></div><div><br>
<br>
Matthias Radestock wrote:<br>
> Owen,<br>
><br>
> Owen Nelson wrote:<br>
>> =INFO REPORT==== 1-Nov-2009::09:13:43 ===<br>
>> alarm_handler: {set,{system_memory_high_watermark,[]}}<br>
>><br>
>> =INFO REPORT==== 1-Nov-2009::09:13:44 ===<br>
>> alarm_handler: {clear,system_memory_high_watermark}<br>
><br>
> These messages indicate that rabbit is running low on memory and is<br>
> attempting to throttle producers.<br>
><br>
> I recommend checking the status of your rabbit using the 'rabbitmqctl<br>
> list_* ...' commands. Chances are you have lots of messages in queues,<br>
> or perhaps lots of queues, exchanges or bindings.<br>
><br>
><br>
> Regards,<br>
><br>
> Matthias.<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>