After reviewing more of the SQL logs ... it's seems more than just a
little odd.
On a cycle, rsyslogd writes maybe 100 rows to the database as a single
connection. After that connect/insert 100/disconnect, it goes into a
cycle connecting/inserting 1 row/disconnecting - but it's the same SQL
for a few hundred records. Almost as if it isn't looking at the new
syslog message that comes into the system and it's using a cache - and
this is even though writing to flat files works just as expected.
Jacob
On 2/5/2014 2:00 PM, Jacob Steinberger wrote:
I have Rsyslogd configured to send data to MySQL and I've found that
only about a third of the records (or less) are actually making it to
MySQL.
What's odd, is I can write all the SQL out to a file (generated via a
template in rsyslog) and all the SQL inserts are there - including the
ones that never made it to MySQL.
Are there any known bugs with Rsyslog 5.8.10 and MySQL? While I
understand this may be considered an old version of rsyslog, it's the
version included in RH6.
Jacob
_______________________________________________
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.
_______________________________________________
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.
