On Thu, Dec 10, 2009 at 06:52:11PM +0100, Rainer Gerhards wrote: > > -----Original Message----- > > From: [email protected] [mailto:rsyslog- > > [email protected]] On Behalf Of Kenneth Marshall > > Sent: Thursday, December 10, 2009 6:43 PM > > To: rsyslog-users > > Subject: Re: [rsyslog] rsyslog 5.3.5 (v5-beta) released > > > > On Thu, Dec 10, 2009 at 04:56:15PM +0100, Rainer Gerhards wrote: > > > Hi Ken, > > > > > > this is a known issue, please see: > > > > > > http://bugzilla.adiscon.com/show_bug.cgi?id=162 > > > > > > If you follow the forum thread in the bug tracker, you'll find some > > request > > > for debug log together with instructions (page 2). If you could send > > me such > > > a log, that would be most helpful. I had begun to set up a postgres > > system > > > myself, but ran out of time... > > > > > > Rainer > > > > > Hi Rainer, > > > > I just read the thread and that is what I am seeing. The error > > that was reported at the end of the thread is actually coming > > from the PostgreSQL DB and not from rsyslog, although the lack > > of commits is triggering the error. I suspect that the tester > > start the database from the same terminal as the rsyslog test > > which is why the error showed up there. > > ah! that explains a lot! I am now waiting for some in-depth debug log. My > hope is that I can quickly fix the situation once I see the control flow. > > Rainer >
I will try and get the debug information between my afternoon meetings. Ken _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
