[syslog-ng]Syslog-NG / sqlsyslogd Date Issues

[Bill Nash]

I'm not familiar with sqlsyslogd, but:

Is there a sanity check being performed on incoming messages, that expects 
a two digit date, typically 01, 02, etc?

- billn

On Fri, 10 Dec 2004, Ronnie Clark wrote:

> Hello all,
>
> I am using syslog-ng on a FreeBSD 5.3 STABLE platform
> with the sqlsyslogd template to log syslog messages to
> a MySQL 4.0.22 database. I noticed that when the date
> rolled from Nov 30 to Dec 1, that the actual messages
> were no longer being recorded. So I verified that the
> messages were being captured in the text files, and
> they were. Now, that the date is the 10th (2 full
> digits), messages are again being logged into the
> database.
> Is this a bug? Anyone else seen this type of behavior?
> I am pretty sure that it is not the OS causing the
> issue, since I have another syslog-ng server running
> on FreeBSD 4.x STABLE and saw the exact same errors on
> that as well.
>
> Any help is greatly appreciated.
>
> Thanks,
> Ron Clark
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Read only the mail you want - Yahoo! Mail SpamGuard.
> http://promotions.yahoo.com/new_mail
> _______________________________________________
> syslog-ng maillist  -  syslog-ng@lists.balabit.hu
> https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
>