Hi, I observed the following behavior and I wanted to know if this behavior is expected:
My configuration looks like: > module(load="imuxsock") > module(load="imklog") > $WorkDirectory /var/spool/rsyslog > > *.* action( > template="RSYSLOG_DebugFormat" > type="omfile" > File="/var/log/syslog-debug" > FileOwner="root" > FileGroup="adm" > ) > > $ModLoad ommysql > *.* :ommysql:mysql.example.org,syslog_db,syslog,secret rsyslog can't reach "mysql.example.org". On rsyslogd start, rsyslog will tell me that the ommysql action was suspended: > action 'action 2' suspended, next retry is Thu Apr 9 20:22:53 2015 [v8.9.0 > try http://www.rsyslog.com/e/2007 ] I guess that's because ommysql cannot talk to the mysql server. Fine. When I now send a message (`logger test`) I am expecting to see this message immediately in /var/log/syslog-debug. That's not going to happen. No messages appear at all. But on 20:22:53, rsyslog seems to wake up and processes all the messages it received between start and now. After all the messages were proceeded, rsyslog seems to be blocked again. The story will repeat... For me it is unexpected that ommysql can block the whole rsyslog instance... -Thomas _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
