Bug 945490 – app-admin/syslog-ng-4.8.1 floods system log with seek error

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Morton Pellung 2024-11-30 22:06:08 UTC]

Upgraded:
     Mon Jun  3 21:35:14 2024 >>> app-admin/syslog-ng-4.6.0
       merge time: 47 seconds.
     Sat Nov 30 22:35:10 2024 >>> app-admin/syslog-ng-4.8.1
       merge time: 49 seconds.

Now:
Nov 30 22:36:05 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:05 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:05 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:07 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:07 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:07 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:12 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:12 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:12 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:12 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:13 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
Nov 30 22:36:14 syslog-ng[2852]: Error invoking seek on file; filename='/dev/kmsg', error='Invalid argument (22)'
...

already reported in https://bugs.gentoo.org/941416#c2
where it was suggested to open a standalone bug for that
-> doing that now

Reproducible: Always

[Comment 1 Holger Hoffstätte 2024-12-01 14:43:45 UTC]

This is already fixed upstream in commit https://github.com/syslog-ng/syslog-ng/commit/2cd1f3abaf077aa0f14de967db55993c06bdad06

Drop that into /etc/portage/patches the log spam is gone.

[Comment 2 Tomáš Mózes 2024-12-03 13:17:15 UTC]

Thanks, patch added to new revision.

[Comment 3 Larry the Git Cow 2024-12-08 18:58:47 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a5e5f715f0e579b36d2b91e16de704ee41e2481c

commit a5e5f715f0e579b36d2b91e16de704ee41e2481c
Author:     Tomáš Mózes <[e-mail]>
AuthorDate: 2024-12-03 13:12:21 +0000
Commit:     Sam James <[e-mail]>
CommitDate: 2024-12-08 18:57:56 +0000

    app-admin/syslog-ng: fix python byte compile, stop spurious kmsg logs
    
    Patch taken from:
    https://github.com/syslog-ng/syslog-ng/pull/5168
    https://github.com/syslog-ng/syslog-ng/issues/5159
    
    Closes: https://bugs.gentoo.org/945490
    Closes: https://bugs.gentoo.org/914968
    Signed-off-by: Tomáš Mózes <[e-mail]>
    Closes: https://github.com/gentoo/gentoo/pull/39576
    Signed-off-by: Sam James <[e-mail]>

 .../syslog-ng-4.8.1-kmsg-invalid-argument.patch    |  53 ++++++
 app-admin/syslog-ng/syslog-ng-4.8.1-r1.ebuild      | 195 +++++++++++++++++++++
 2 files changed, 248 insertions(+)

[Comment 4 Xoores 2025-01-03 17:00:55 UTC]

(In reply to Tomáš Mózes from comment #2)
> Thanks, patch added to new revision.

Can confirm the 4.8.1-r1 does fix the issue.

Could we please unmask the 4.8.1-r1? Or perhaps mask the "spammy" 4.8.1...

As things are currently, the latest unmasked version is just a ticking timebomb waiting for some unsuspecting sucker (like me today) to upgrade & reboot, leaving me wondering what happened. :-)