[rsyslog-notify] Forum Thread: rsyslog blocked when backend database down - (Mode 'post')

[noreply at adiscon.com]

User: tboyer 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24998#p24998

Message: 
----------
Running 8.4.1 on RHEL6.5.  We're writing the logs to two places - basic
text using the usual DYNmessages template:

$template
DYNmessages,"/var/log/hosts/%fromhost%/%syslogfacility-text%.%$year%.%$month%.%$day%"

and then to a couple of databases, using filters:

if $fromhost-ip contains "10.0.1." or $fromhost-ip contains "10.0.2."  then
{ action(type="ommysql" server="127.0.0.1" db="rsyslogdlinux" uid=""
pwd="") stop }
if $fromhost-ip contains "10.0.3." or $fromhost-ip contains "10.0.4."  then
{ action(type="ommysql" server="127.0.0.1" db="rsyslogdesxi" uid="" pwd="")
stop }
action(type="ommysql" server="127.0.0.1" db="rsyslogwin" uid="" pwd="")

and all is fine - until we try to verify/clean up the database.  Database
cleanup takes more than three hours, and during that time nothing is
written to the text files.

I understand why nothing gets written to the database, of course, but is
there something I can do - a timeout or something similar - that will write
to the text files even when the backend is unavailable?

Thanks...