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

Dmitri Minaev minaev at gmail.com
Fri Dec 30 15:34:38 GMT 2011

Thank you very much. I will install it today or tomorrow, but our
system was switched over to another installation. Besides, I do not
expect intensive load till after 10 January, the end of Russian New
Year vacations.

But I am still curious about the fact that until about two months ago
our experience with RabbitMQ was very good. We had version 2.1 or 2.2
then and it worked fine. The problems started when I moved Rabbit to
another server and upgraded it. Either the bug was introduced between
versions 2.2 and 2.6.1, or it is related to some changes in the server
environment. Is it possible to find out whether versions 2.1-2.2 were
also influenced by the problem?

On 30 December 2011 18:02, Matthias Radestock <matthias at rabbitmq.com> wrote:
> Dmitri,
> On 30/12/11 12:11, Matthias Radestock wrote:
>> When the tcp stack notifies the acceptor of an error
>> other than 'closed', the acceptor carries on but does not invoke
>> prim_inet:async_accept/2 to be notified of the next connection attempt.
>> I will file a bug for this. Should be easy to fix, though we cannot be
>> certain that this is definitely the problem.
> Here's a proposed fix:
> http://hg.rabbitmq.com/rabbitmq-server/rev/ca0392ca0fc1
> I am attaching a tcp_acceptor.beam with that fix, compiled for R15, that you
> can drop in place of the existing file. I'd be interested a) if that solves
> the problem for you, and b) what error gets logged - watch out for s.t. like
> =ERROR REPORT==== 30-Dec-2011::13:45:01 ===
> failed to accept TCP connection on [::]:5672: some_error
> in the logs.
> Regards,
> Matthias.

With best regards,
Dmitri Minaev

More information about the rabbitmq-discuss mailing list