[rsyslog-notify] Forum Thread: Re: Queue not working on Mongodb restart - (Mode 'reply')

[noreply at adiscon.com]

User: dlang 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24187#p24187

Message: 
----------
the best way to tell what's happening with the queues is to configure
impstats and have it write to a dedicated file (as opposed to generating
log messages in the normal queues)

rsyslog first queues into RAM, and only after the RAM queue fills does it
start writing to disk. You can configure rsyslog to dump the RAM queue to
disk when it's shutdown, but you need to make sure your shutdown script
gives it time to write everything out (most shutdown scripts send a
graceful shutdown signal (-15) to processes, wait a few seconds, then send
an immediate shutdown signal (-9) that aborts any processing that the
service is doing)

I suspect that in your case you are loosing the logs in RAM when you
restart rsyslog.

You should try sending rsyslog a HUP signal instead of restarting it. That
should cause it to close and reopen all outputs, which should reestablish
the connection to mongodb

It sounds as if there is a problem in the mongodb module that's causing it
to not detect the connection is broken and reestablish it.