[rabbitmq-discuss] RabbitMQ 3.0.2 stops logging, but otherwise looks healthy?

Jeffery, Mark MJeffery at fnb.co.za
Tue Jul 16 20:19:00 BST 2013


Assuming Linux, what does ls -latr show in the fd directory in the rabbitmq process's directory under /proc ?

Matt Pietrek <mpietrek at skytap.com> wrote:

This is admittedly a shot in the dark, and with limited repro details, but asking if somebody else has seen this.

We run our clustered RabbitMQ 3.0.2 brokers in production without restarts for months at a time. Everything is looking good - No memory leaks, no out-of-disk-space, etc...

However, in looking at the rabbit@<node>.log and rabbit@<node>-sasl.log files, I noticed that at some point (e.g. a month earlier), no new entries were being added to the log file. Normally there's a steady stream of new connections and connection drops.

I've listed the open file handles from the rabbitmq beam instance and I still see live file handles for the log files.

Anybody have any idea what might be happening? And better still, how we might kick things without restarting the broker?



To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: 

If you are unable to access the Disclaimer, send a blank e-mail to
firstrandbankdisclaimer at fnb.co.za and we will send you a copy of the Disclaimer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130716/354d6c70/attachment.htm>

More information about the rabbitmq-discuss mailing list