Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#28734 - [syslog-ng] 3.3.4-2 writes garbled messages to logs
Attached to Project:
Arch Linux
Opened by Jose Marino (oniram) - Thursday, 01 March 2012, 17:40 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 01 March 2012, 23:27 GMT
Opened by Jose Marino (oniram) - Thursday, 01 March 2012, 17:40 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 01 March 2012, 23:27 GMT
|
DetailsDescription:
Lately I've been seen some weird messages in some log files in /var/log/. Not all the messages are garbled, I'd say it happens when a burst of kernel messages occur. To demonstrate the problem I attach the logs produced when I unplug and re-plug a USB mouse. For simplicity the logs only include the messages produced during the unplug/plug of the USB mouse. This is what I did: - pacman -Syu and do a fresh reboot. - Copy dmesg, and /var/log/ files. - At 12:11:48 I unplug the USB mouse. - Around 12s later I plug the USB mouse. - Copy dmesg, and /var/log/ files. The log files I attach are: - Output of dmesg, which appears to report the kernel messages correctly. - Contents of /var/log/kernel.log - Contents of /var/log/messages.log - Contents of /var/log/everything.log I run arch linux in a Dell Latitude E6410 laptop. I run a custom kernel, which is a vanilla stable kernel from git (3.2.9) + a few patches from 3.3-rc that enable functionality of the laptop's mousepad (d4b347..7cf801). I'm using systemd as my init system: $ pacman -Qs systemd local/libsystemd 43-3 systemd client libraries local/systemd 43-3 systemd and service manager local/systemd-arch-units 20120208-1 Arch specific Systemd unit files $ systemctl status syslog-ng.service syslog-ng.service - System Logger Daemon Loaded: loaded (/lib/systemd/system/syslog-ng.service; enabled) Active: active (running) since Thu, 01 Mar 2012 12:09:28 -0500; 27min ago Process: 264 ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service (code=exited, status=0/SUCCESS) Main PID: 278 (syslog-ng) CGroup: name=systemd:/system/syslog-ng.service └ 278 /usr/sbin/syslog-ng -F |
dmesg.log
This task depends upon
Closed by Andrea Scarpino (BaSh)
Thursday, 01 March 2012, 23:27 GMT
Reason for closing: Not a bug
Additional comments about closing: http://www.mail-archive.com/arch-dev-pub lic%40archlinux.org/msg18912.html
Thursday, 01 March 2012, 23:27 GMT
Reason for closing: Not a bug
Additional comments about closing: http://www.mail-archive.com/arch-dev-pub lic%40archlinux.org/msg18912.html
I just rebooted the laptop using sysvinit as the init system and the problem goes away.
if i'm correct if you are using systemd then you dont need syslog anymore.
since systemd >38 systemd-journal is there and it is a replacement for syslog
for more info read:
- http://www.mail-archive.com/arch-dev-public%40archlinux.org/msg18912.html
- http://cgit.freedesktop.org/systemd/systemd/tree/NEWS
It turns out the problem was caused by systemd journal and syslog-ng trying to read from /dev/log at the same time. I mistakenly thought that systemd and syslog-ng were able to coexist by default.
For now I've decided to disable syslog-ng and give systemd journal a try.
I'll close this, since it is not really a bug, just a syslog-ng configuration issue.
source src {
unix-dgram("/dev/log");
internal();
file("/proc/kmsg");
};