RabbitMQ suddenly stops accepting connections

[Max Morogovsky]

Hi,

We're using RabbitMQ server 3.6.5 with Erlang 19, RabbitMQ Net client v3.5.7, used by .net 4.6.1 app.

We're experiencing an issue when once in a while RabbitMQ stops accepting connections and returns BrokerUnreachableException ("No connection could be made because the target machine actively refused it") to the worker that tries to connect. Most of the times recycling the app doesn't help, and only a restart to the RabbitMQ server brings it back to life.
The RabbitMQ log is full with messages that look as following:

 =WARNING REPORT==== 26-Jan-2017::15:17:48 ===

closing AMQP connection <0.29552.177> (IP:Port -> IP:RabbitMQport):

client unexpectedly closed TCP connection

No suspicious windows event log entries are detected,

Any idea what direction should I continue to investigate in? 

Is there any other, more verbose logs RabbitMQ may write somewhere regarding the state of the service?

Will appreciate any help.

Thanks,

Max

[Michael Klishin]

According to the broker log it's the client that closes TCP connection without closing AMQP one first.

If there is a proxy or load balancer involved, investigate its logs and idle timeout settings.

Also see how many open file descriptors your 

node has and how close it is to the OS-enforced limit:

http://rabbitmq.com/networking.html.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.