[rabbitmq-discuss] RabbitMQ 2.8.2 - Service Crash on Windows 2008 R2

Icidis ryan at nutcracker.co.za
Tue Aug 21 06:26:46 BST 2012


Matthias Radestock-3 wrote
> 
> On 20/08/12 18:17, Emile Joubert wrote:
>> On 20/08/12 14:36, Ryan Gunn wrote:
>>> ** Reason for termination ==
>>> ** {accept_failed,enfile}
>>
>> This is a POSIX error code meaning you have run out of file descriptors.
>> The errors that follow are a consequence of this. You should be able to
>> raise the limit by setting the ERL_MAX_PORTS variable. Make sure you
>> really need to open that many connections and that your application is
>> not leaking connections. I see that connections are accepted at an
>> alarming rate just before the error.
> 
> Alas rabbit generally refuses to accept more connection when file 
> descriptors are scarce. I wonder why this isn't happening here.
> 
> What limits are reported by 'rabbitmqctl status'?
> 
> Matthias.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at .rabbitmq
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> 

Good Day Emile & Matthias,

I've attached the rabbitmqctl status report, I will go through all my
application logs to see if any are leaking connections.

http://rabbitmq.1065348.n5.nabble.com/file/n21529/RabbitMQ_Limits.txt
RabbitMQ_Limits.txt 

Thanks for all your help

Ryan Gunn




--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/RabbitMQ-2-8-2-Service-Crash-on-Windows-2008-R2-tp21512p21529.html
Sent from the RabbitMQ mailing list archive at Nabble.com.


More information about the rabbitmq-discuss mailing list