[rabbitmq-discuss] RabbitMQ hangs, does not accept connections

Dmitri Minaev minaev at gmail.com
Mon Mar 26 06:45:45 BST 2012

On 9 March 2012 16:37, Simon MacMullen <simon at rabbitmq.com> wrote:
> On 09/03/12 07:57, Dmitri Minaev wrote:

>> If I understand correctly, the number of file descriptors used by
>> RabbitMQ in normal situation is roughly equal to the number of
>> `rabbitmqctl list_connections` + some constant (~30)? In case of that
>> hanging server, the number of AMQP connections never was close to the
>> FD limit (ulimit -n is 1024, fs.file-max = 1605698). The graph
>> reflecting  the number of open AMQP connections is attached to this
>> message.
> It's not really a constant, but to a first approximation, yes.
> Ultimately, the error I saw being passed up from the OS was ENFILE - that's
> pretty unambiguous :)
> It's possible that if you're churning connections then "closed" connections
> in FIN_WAIT2 could account for the majority of the used FDs. In 2.8.0 we'll
> set SO_LINGER to 0 to prevent this.

I am still not sure about the role of the file descriptors in this
event. Last Friday, our Rabbit died again. Until the very last moment
the number of open file descriptors as reported by the management
plugin was 143 out of the total available number of 32765. It was
RabbitMQ v.2.7.0. On that same day I have upgraded to 2.8.1. Will
report on its behaviour later.

With best regards,
Dmitri Minaev

More information about the rabbitmq-discuss mailing list