9 Apr
2008
9 Apr
'08
10:01 p.m.
Balazs Scheidler did thus speak on 4/9/2008 2:31 PM:
So much about heuristics, the reason for this is that syslog-ng tries to parse multiple date/time formats and one of them has a year right after the original BSD timestamp.
So syslog-ng assumes that the message given is from year 1234, which cannot be represented by unix timestamps (range 1970 - 2038), and that's the reason for the garbled timestamp.
Can you check if this patch fixes it:
commit 476a72e1d927d3404e22866bd9310c6013938d1b Author: Balazs Scheidler <bazsi@balabit.hu> Date: Wed Apr 9 21:30:50 2008 +0200
[Snip: Patch] I have applied the patch and verified that all of the previously failing test cases I had are now working correctly. Thank you! -- Christopher Cashell