Gravatar for tatiana.morales@abc.virginia.gov

Question by tmorales, Dec 7, 2018 6:46 PM

RabbitMQ stopped working - file descriptor limit alarm set

RabbitMQ stopped working with the below message:

=WARNING REPORT==== 5-Dec-2018::17:05:18 ===

file descriptor limit alarm set.

********************************************************************

*** New connections will not be accepted until this alarm clears ***

***************************

We also saw the below exceptions on the Sitecore logs:

1. Exception: RabbitMQ.Client.Exceptions.ProtocolVersionMismatchException Message: AMQP server protocol negotiation failure: server version unknown-unknown, client version 0-9

2. Exception: System.Net.Sockets.SocketException Message: No connection could be made because the target machine actively refused it 127.0.0.1:5682

When this happens all publishing stops.

The first day we noticed, we re-started the service and RabbitMQ started working again. Then after a few hours stopped working again with the same error. We re-started once more and it started working.

In RabbitMQ, under nodes, we can see File descriptors 880 in use/8192 available . At the time of this email.

We had this configuration for a long time (years). This is the first time we see this error. We are monitoring closely but other than re-staring and waiting to fail again not sure of what to do.

There were no errors in the Event viewer. Sitecore CM, CES and RabbitMQ run in the same server.

Any idea on what to look for? or configurations to change?

I would think that service should recover on its own after the alarm clears but that doesn't seem to be the case.

Current Coveo for Sitecore version: 4.1.224.6

Current Sitecore version: 8.1.160519

Thanks

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Dec 13, 2018 11:03 AM

This is a question better suited for Coveo Support. Could you please create a support ticket?

Thanks.

0 Reply
Ask a question