[Bug 809916] New: systemd floods "/var/log/messages" when syslog-ng is used
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c0 Summary: systemd floods "/var/log/messages" when syslog-ng is used Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: 64bit OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bugzilla@singvogel.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0 When booting openSUSE-12.3 and having syslog-ng chosen, the systemd floods /var/log/messages when the same message: systemd[1]: syslog-ng.service start request repeated too quickly, refusing to start. This message is around 1100 times in /var/log/messages. This only happens when booting only. The syslog-ng daemon is running as expected after boot: 1x. The fault is the number of same messages in /var/log/messages. Reproducible: Always This is a openSUSE-12.3 bugzilla entry, but I cannot choose the 12.3 in selection field at the moment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c Klaus Singvogel <bugzilla@singvogel.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jw@suse.com Found By|--- |Community User -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c Xiaolong Li <xlli@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xlli@suse.com AssignedTo|bnc-team-screening@forge.pr |mt@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c1 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |pczanik@genesi-usa.com InfoProvider| |bugzilla@singvogel.com --- Comment #1 from Marius Tomaschewski <mt@suse.com> 2013-03-20 07:56:32 UTC --- Could you provide the outputs of "systemctl status syslog.service" and "systemctl status syslog-ng.service" please? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c2 Klaus Singvogel <bugzilla@singvogel.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |bugzilla@singvogel.com InfoProvider|bugzilla@singvogel.com | --- Comment #2 from Klaus Singvogel <bugzilla@singvogel.com> 2013-03-20 08:00:19 UTC --- As requested: "systemctl status syslog.service" syslog-ng.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled) Active: active (running) since Sun, 2013-03-17 00:32:01 CET; 3 days ago Process: 1335 ExecStartPre=/usr/sbin/syslog-ng-service-prepare (code=exited, status=0/SUCCESS) Main PID: 1341 (syslog-ng) CGroup: name=systemd:/system/syslog-ng.service â 1341 /usr/sbin/syslog-ng -F --------------------------------------------- systemctl status syslog-ng.service syslog-ng.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled) Active: active (running) since Sun, 2013-03-17 00:32:01 CET; 3 days ago Process: 1335 ExecStartPre=/usr/sbin/syslog-ng-service-prepare (code=exited, status=0/SUCCESS) Main PID: 1341 (syslog-ng) CGroup: name=systemd:/system/syslog-ng.service â 1341 /usr/sbin/syslog-ng -F --------------------------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c3 --- Comment #3 from peter czanik <pczanik@genesi-usa.com> 2013-03-20 08:13:09 UTC --- I have also seen it once, but at that time I could not figure out how to reproduce it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c4 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED See Also| |https://bugzilla.novell.com | |/show_bug.cgi?id=805309 --- Comment #4 from Marius Tomaschewski <mt@suse.com> 2013-03-20 08:15:23 UTC --- Basically, the syslog-ng start is requested by each log message via syslog.socket dependency. Did you increased the systemd log level, so it logs each of these attempts? But finally, syslog-ng should be able to suppress them. The default config contains suppress(30) for /var/log/messages: destination messages { file("/var/log/messages" suppress(30) owner(-1) group(-1) perm(-1)); }; Does your config contain it, could you attach /etc/syslog-ng/syslog-ng.conf please? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c5 --- Comment #5 from Klaus Singvogel <bugzilla@singvogel.com> 2013-03-20 08:26:11 UTC --- Created an attachment (id=530586) --> (http://bugzilla.novell.com/attachment.cgi?id=530586) syslog-ng.conf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c6 --- Comment #6 from Klaus Singvogel <bugzilla@singvogel.com> 2013-03-20 08:27:02 UTC --- No, I didn't change systemd log level - btw. didn't know that this is possible. Yes, I know that "suppress(30)" should reduce the number of messages, and checked it before opening the bugzilla entry. But a) suppressing them is not the solution b) suppress(30) is enabled and doesn't work. Yes, I have a modified syslog-ng.conf file, but there are no changes, which are related here. But for sake of completeness, I've attached my modified syslog-ng.conf - see above -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c7 --- Comment #7 from Marius Tomaschewski <mt@suse.com> 2013-03-20 08:54:33 UTC --- (In reply to comment #6)
No, I didn't change systemd log level - btw. didn't know that this is possible.
OK, then I don't need to ask if you changed the /etc/systemd/{system.conf,journald.conf} somehow or set some systemd.* boot parameters (cat /proc/cmdline)? ;-)
Yes, I know that "suppress(30)" should reduce the number of messages, and checked it before opening the bugzilla entry. But a) suppressing them is not the solution
Not? I fear it is the only solution available. Except of fixing the program that generates the message to not log same message again and again -> something for "osc bugowner systemd" in this case, not for "osc bugowner syslog-ng".
b) suppress(30) is enabled and doesn't work.
Not? On my host the suppression generally works: # grep suppress /var/log/messages shows me message lines like: systemd: Last message 'Deactivating swap /d' repeated 2 times, suppressed by syslog-ng # for i in {1..30} ; do logger baaaaaaaaarrrrrrrr ; done # logger flood end # grep baaa /var/log/messages ...: baaaaaaaaarrrrrrrr ...: Last message 'baaaaaaaaarrrrrrrr' repeated 29 times, suppressed by syslog-ng on ...
Yes, I have a modified syslog-ng.conf file, but there are no changes, which are related here.
But for sake of completeness, I've attached my modified syslog-ng.conf - see above
Yes... your config looks fine and contains the suppress option for /var/log/messages. In your message there is also no "[ xxx.yyyyyyyy]" kernel like monotonic clock timestamp in the front of the message which could make them look unique ... right? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c8 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mt@suse.com |fcrozat@suse.com --- Comment #8 from Marius Tomaschewski <mt@suse.com> 2013-03-20 09:03:42 UTC --- OK, IMO I've verified that syslog-ng suppression works fine and there seems to be no misconfiguration causing it on syslog-ng side. Reassign to systemd maintainer - Frederic, any Idea? Either there is come config option set somehow or systemd tends to flood here logging a message while every of the 1100 checks if syslog daemon is already or not; it should do things like this only in debug mode IMO. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c9 --- Comment #9 from Klaus Singvogel <bugzilla@singvogel.com> 2013-03-20 09:06:19 UTC ---
if you changed the /etc/systemd/{system.conf,journald.conf} somehow or set some systemd.* boot parameters (cat /proc/cmdline)?
No change made.
Not? I fear it is the only solution available.
This is only fixing the symptoms not the cause.
Not? On my host the suppression generally works:
sorry, for misunderstanding. At my side suppress() works in general too: # grep -c suppress /var/log/messages 4 but suppress() doesn't work for this issue.
In your message there is also no "[ xxx.yyyyyyyy]" kernel like monotonic clock timestamp in the front of the message which could make them look unique ... right?
I cut it away: unnecessary information for bug report when boot time, and sytem time was. But I think this is the reason why suppress() doesn't work: the kernel time is measured in microseconds, and is part of the log message too. So the message is constantly changing, and suppress() cannot find duplicates therefore. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c10 --- Comment #10 from Juergen Weigert <jw@suse.com> 2013-03-20 09:16:51 UTC --- *** Bug 810331 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=810331 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c11 --- Comment #11 from Frederic Crozat <fcrozat@suse.com> 2013-03-20 09:25:12 UTC --- It might be worth testing Fedora patch http://pkgs.fedoraproject.org/cgit/syslog-ng.git/tree/syslog-ng-3.3.6-syslog... to ensure systemd considers syslog-ng "up and running" only when the PID file is created. Also, comparing what Fedora is doing, they are using : file ("/proc/kmsg" program_override("kernel") flags(kernel)); instead of: file ("/proc/kmsg" program_override("kernel")); (not sure it is related..) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c12 --- Comment #12 from peter czanik <pczanik@genesi-usa.com> 2013-03-20 10:39:01 UTC --- @Frederic: the following branch for the upcoming syslog-ng 3.5 version has some patches, which will help syslog-ng to emit proper systemd status messages. It's currently unmerged and untested. Will this be a proper resolution for the problem, once available? https://github.com/algernon/syslog-ng/commits/feature/3.5/systemd/goodies -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c13 --- Comment #13 from Frederic Crozat <fcrozat@suse.com> 2013-03-20 11:46:26 UTC --- (In reply to comment #12)
@Frederic: the following branch for the upcoming syslog-ng 3.5 version has some patches, which will help syslog-ng to emit proper systemd status messages. It's currently unmerged and untested. Will this be a proper resolution for the problem, once available? https://github.com/algernon/syslog-ng/commits/feature/3.5/systemd/goodies
probably. But maybe adding PID option would be enough -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c14 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |werner@suse.com InfoProvider| |pczanik@genesi-usa.com --- Comment #14 from Dr. Werner Fink <werner@suse.com> 2013-11-27 13:10:46 UTC --- (In reply to comment #13) Are there any news? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c15 peter czanik <pczanik@genesi-usa.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|pczanik@genesi-usa.com | --- Comment #15 from peter czanik <pczanik@genesi-usa.com> 2013-11-27 13:37:00 UTC --- syslog-ng 3.5.1 is released, but without man pages, so I'm waiting for 3.5.2 before sending it to Base:System and Factory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|SUSE Other |openSUSE 12.3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com