I have working rsyslog (v5.8.10) with simple omoracle configuration pushing data to a single Oracle 11g database table. The configuration is working but I'm a bit puzzled about the behaviour of the omoracle plugin where I only ever see the second last log event written to the database table ...however, *all* log events (including last one) are written to local messages file immediately
In my testing, with "$OmoracleBatchSize" option set to lowest possible value of "1" (I discovered setting to '0' is *not* a good idea), the omoracle plugin processes one log message at a time however the last log event is not written to the database ...unless another arrives or rsyslogd is shut down. In the latter case, all outstanding log events, including the shut down messages, are written to the database. Is this (description above) the expected behaviour or should all log messaages be completely processed and written to database as they arrive same as for local messages file? I had a look at the omoracle code but, sadly, my skills in that area are poor. I have searched for information on the behaviour I'm seeing but no luck finding any answers hence my decision to pose a question on this list - any feedback greatly appreciated. Regards, Damian _______________________________________________ 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.
