Bug#729575: syslog-ng-core: bogus date for kernel messages
* Gergely Nagy alger...@balabit.hu, 2013-11-21, 14:42:
Hm... I have not been able to reproduce it yet...
I suspect the bug might be architecture-specific. I can reproduce it on i386,
but not on amd64.
can you change your template to include ${.linux.timestamp} too, and send me a
sample?
With
template($YEAR-$MONTH-$DAY $HOUR:$MIN:$SEC (${.linux.timestamp})
$MSG\n);
I've got this:
1961-02-05 14:29:55 (2278410933) fb1: VESA VGA frame buffer device
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729575: syslog-ng-core: bogus date for kernel messages
Control: tag -1 upstream Found the issue, I'm pushing a fix into git, fixed package should hit unstable early next week latest. Thanks for the report and the assistance! -- |8] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729575: syslog-ng-core: bogus date for kernel messages
Jakub Wilk jw...@debian.org writes:
* Gergely Nagy alger...@balabit.hu, 2013-11-15, 17:05:
syslog-ng has just logged this:
1961-02-05T20:15:59+01:00 borsuk kernel: usb 1-2: USB disconnect, device
number 5
The timestamp is obviously bogus. My system date is correct, and
non-kernel messages are logged with correct timestamps.
According to my logs this started happening after the 3.3.9-1 -
3.5.1-1
upgrade.
Likely not relevant, but are you using systemd?
Nope, the good old sysvinit.
Do all kernel messages have bogus dates, or only a few ones?
All of them.
Hm... I have not been able to reproduce it yet... can you change your
template to include ${.linux.timestamp} too, and send me a sample?
--
|8]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729575: syslog-ng-core: bogus date for kernel messages
Jakub Wilk jw...@debian.org writes:
* Gergely Nagy alger...@balabit.hu, 2013-11-21, 14:42:
Hm... I have not been able to reproduce it yet...
I suspect the bug might be architecture-specific. I can reproduce it
on i386, but not on amd64.
Mhm, great, then I have a suspicion where the problem lies.
can you change your template to include ${.linux.timestamp} too, and
send me a sample?
With
template($YEAR-$MONTH-$DAY $HOUR:$MIN:$SEC (${.linux.timestamp})
$MSG\n);
I've got this:
1961-02-05 14:29:55 (2278410933) fb1: VESA VGA frame buffer device
Good, good, so parsing is correct, computing the date is off, though.
Thanks, this narrows things down considerably!
--
|8]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729575: syslog-ng-core: bogus date for kernel messages
Jakub Wilk jw...@debian.org writes: Package: syslog-ng-core Version: 3.5.1-1 syslog-ng has just logged this: 1961-02-05T20:15:59+01:00 borsuk kernel: usb 1-2: USB disconnect, device number 5 The timestamp is obviously bogus. My system date is correct, and non-kernel messages are logged with correct timestamps. According to my logs this started happening after the 3.3.9-1 - 3.5.1-1 upgrade. Likely not relevant, but are you using systemd? Do all kernel messages have bogus dates, or only a few ones? -- |8] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729575: syslog-ng-core: bogus date for kernel messages
* Gergely Nagy alger...@balabit.hu, 2013-11-15, 17:05: syslog-ng has just logged this: 1961-02-05T20:15:59+01:00 borsuk kernel: usb 1-2: USB disconnect, device number 5 The timestamp is obviously bogus. My system date is correct, and non-kernel messages are logged with correct timestamps. According to my logs this started happening after the 3.3.9-1 - 3.5.1-1 upgrade. Likely not relevant, but are you using systemd? Nope, the good old sysvinit. Do all kernel messages have bogus dates, or only a few ones? All of them. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729575: syslog-ng-core: bogus date for kernel messages
Package: syslog-ng-core Version: 3.5.1-1 syslog-ng has just logged this: 1961-02-05T20:15:59+01:00 borsuk kernel: usb 1-2: USB disconnect, device number 5 The timestamp is obviously bogus. My system date is correct, and non-kernel messages are logged with correct timestamps. According to my logs this started happening after the 3.3.9-1 - 3.5.1-1 upgrade. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.11-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages syslog-ng-core depends on: ii init-system-helpers 1.13 ii libc62.17-95 ii libcap2 1:2.22-1.2 ii libevtlog0 0.2.12-6 ii libglib2.0-0 2.36.4-1 ii libivykis0 0.36.2-1 ii libnet1 1.1.6+dfsg-2 ii libpcre3 1:8.31-2 ii libssl1.0.0 1.0.1e-4 ii libsystemd-daemon0 204-5 ii libwrap0 7.6.q-24 ii util-linux 2.20.1-5.5 Versions of packages syslog-ng-core recommends: ii logrotate 3.8.6-1 Versions of packages syslog-ng-core suggests: pn syslog-ng-mod-amqp none pn syslog-ng-mod-geoipnone pn syslog-ng-mod-json none pn syslog-ng-mod-mongodb none pn syslog-ng-mod-redisnone pn syslog-ng-mod-smtp none pn syslog-ng-mod-sql none pn syslog-ng-mod-stompnone -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
