Okay, I will take a look at the output plugin to see where it makes the most sense to fix this. A trigger will always work, but would require every DB to setup and maybe having the plugin perform the truncation would be better. Thank you for the recommendation.
Regards, Ken On Fri, Sep 25, 2009 at 03:30:58PM +0200, Rainer Gerhards wrote: > Actually, it should have dropped this message, but that depends on the > configuration. In general, rsyslog does not know about the schema. And to be > more precise, we are not really talking about rsyslogd itself but rather the > output plugin. Every output plugin can perform its own checks. > > But the best answer probably is to use a trigger ;) > > Rainer > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > Kenneth Marshall > > Sent: Friday, September 25, 2009 2:55 PM > > To: [email protected] > > Subject: [rsyslog] rsyslog bug - logging stops after a DB error > > > > I just looked at our PostgreSQL DB for our rsyslog system and > > the following error was logged: > > > > ERROR: value too long for type character varying(60) > > STATEMENT: insert into SystemEvents (Message, Facility, > > FromHost, Priority, DeviceReportedTime, ReceivedAt, > > InfoUnitID, SysLogTag) values ('', 1, 'mh2.mail.rice.edu', 5, > > '2009-09-25 00:11:39', '2009-09-25 00:11:39', 1, > > '///////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > ////////////////////////////////////////////////////////////// > > /////////////////////////////////////////////////////////////////') > > > > The problem is not so much the error but that it stopped logging > > to the database. I had to restart rsyslog to get it to start logging > > once more. Should rsyslog check that its values match the schema or > > should I need to setup a trigger in the DB to handle off-the-wall > > input. > > > > Regards, > > Ken > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
