[rabbitmq-discuss] rabbitmq 2.8.2 beam process consumes 100% of one cpu in tight epoll_wait loop

Emile Joubert emile at rabbitmq.com
Wed Jun 20 15:13:10 BST 2012


Hi Con,

On 18/06/12 18:29, Con Zyor wrote:
> The queues directory has not yet been re-created by rabbitmq. This
> rabbitmq-server is part of a Chef installation. I will post back if the
> problem reoccurs. After the purge, the ntop output looks like this:

Yes please do let us know if you see this again.

That command should have been "etop -node" followed by the node of the
broker (typically rabbit at host). By default "etop" reports about the node
it is running, which is not very useful.


-Emile




More information about the rabbitmq-discuss mailing list