<br><br><div class="gmail_quote">On Tue, Nov 13, 2012 at 8:32 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Lars,<div><div class="h5"><br>
<br>
On 13/11/12 18:31, Lars Windolf wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I was asked by Matthias Rodestock to submit my experience [1] with<br>
100% CPU usage when file descriptors are used up.<br>
<br>
My setup:<br>
- Recent Chef with Ubuntu rabbitmq-server package 2.8.4-1<br>
<br>
Steps to reproduce:<br>
1.) Set ulimit -n to low value (e.g. default of 1024)<br>
2.) Connect a lot of chef nodes, do a lot of stuff<br>
3.) Wait 2 or 3 days<br>
<br>
After this memory usage goes up and at some time it starts eating CPU.<br>
It does stop working then. Listing the queues doesn't work anymore.<br>
Restarting the service doesn't help. "rabbitmqctl report" shows ~100%<br>
used file descriptors.<br>
<br>
Increasing the ulimit and restarting RabbitMQ immediately helps.<br>
<br>
Best Regards,<br>
Lars<br>
<br>
[1] <a href="http://lzone.de/Solving+100%25+CPU+usage+of+Chef" target="_blank">http://lzone.de/Solving+100%<u></u>25+CPU+usage+of+Chef</a><br>
</blockquote>
<br></div></div>
Thanks for submitting this report. The bug in question got fixed in RabbitMQ 2.8.5. It would be great if a) you were able to confirm that (*), and b) help disseminate that information to the Chef users.<br>
<br>
I guess people are still running into this because Debian testing and Ubuntu Quantal ship with 2.8.4.<br></blockquote><div><br>Thanks for the explanation. I updated my post to hint on the upgrade and <br>will retest as soon as Ubuntu/Debian update to 2.8.5 or larger.<br>
</div></div><br>Thanks a lot!<br><br>Cheers,<br>Lars<br>