[rabbitmq-discuss] RabbitMQ actively refuses connections after connectity issues

Simon MacMullen simon at rabbitmq.com
Tue Aug 2 10:53:34 BST 2011

On 02/08/11 10:44, Alfonso Pantoja wrote:
> More info:
> when we had the problem, in RabbitMQ web admin we could see that file
> descriptors monitor were in red (file descriptors were near the
> maximum)

Well that's basically your problem - when RabbitMQ runs out of file 
descriptors it simply can't accept any more TCP connections. In practice 
it will stop accepting connections slightly before it runs out 
completely, to give itself some wriggle room when writing new files.

This is a pure OS-level limitation, Rabbit gives you some monitoring of 
the situation but that's it.

The most likely problem was that something was holding connections open 
- check the connections page in mgmt to see what that was.

Ubuntu has a fairly low limit on file descriptors by default (1000) - if 
you think you could legitimately want to accept more than ~800 
connections at once you might want to add something like:

rabbitmq        soft    nofile          100000
rabbitmq        hard    nofile          100000

to /etc/security/limits.conf and restart Rabbit.

Cheers, Simon

Simon MacMullen
RabbitMQ, VMware

More information about the rabbitmq-discuss mailing list