[rabbitmq-discuss] RabbitMQ running at 100% CPU.

Michael Arnoldus chime at mu.dk
Thu Mar 13 14:35:50 GMT 2008


Matthias,

And more info - it seems the error returned is 32 which in errno.h is  
EPIPE.

In the manual page for writev it says:

[EPIPE]            An attempt is made to write to a socket of type  
SOCK_STREAM that is not connected to a peer socket.

Does this make any sense to you at all? Do you have an idea if I  
should continue investigating the erlang runtime system or do you  
think it is something inside Rabbit?

Michael

On Mar 13, 2008, at 10:49 , Matthias Radestock wrote:

> Michael,
>
> Michael Arnoldus wrote:
>> I've kept it running. I'm sure if I restart erlang everything will   
>> just run perfectly, but I'd rather use this incident to try to  
>> find  the problem if it's possible. However i'm running out of  
>> things to  try, so any suggestions will be welcome.
>
> Try running strace on the Erlang process, to see whether it's stuck  
> in some busy loop making system calls.
>
>> If nobody has any other suggestions I'd be inclined to upgrade to  
>> the  latest version of erlang. Does anybody have any experince  
>> using this  with Rabbit?
>
> Several people have been running with R12B in their development  
> environments without any problems. It should be fine, but we haven't  
> done any thorough testing with it.
>
>
> Matthias.





More information about the rabbitmq-discuss mailing list