https://bugzilla.novell.com/show_bug.cgi?id=809916 https://bugzilla.novell.com/show_bug.cgi?id=809916#c Klaus Singvogel 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#c1 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |pczanik@genesi-usa.com InfoProvider| |bugzilla@singvogel.com --- Comment #1 from Marius Tomaschewski 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#c3 --- Comment #3 from peter czanik 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#c5 --- Comment #5 from Klaus Singvogel 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#c7 --- Comment #7 from Marius Tomaschewski 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#c9 --- Comment #9 from Klaus Singvogel 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#c11 --- Comment #11 from Frederic Crozat 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#c13 --- Comment #13 from Frederic Crozat 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#c14 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |werner@suse.com InfoProvider| |pczanik@genesi-usa.com --- Comment #14 from Dr. Werner Fink 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#c Dr. Werner Fink 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.