Summary: | app-admin/syslog-ng-4.2.0: invalid pid values shown in log | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rolf Eike Beer <eike> |
Component: | Current packages | Assignee: | Tomáš Mózes <hydrapolic> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | floppym, hydrapolic, hyedad, joost, proxy-maint, rtgill82 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/syslog-ng/syslog-ng/issues/4597 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 923176, 924000 | ||
Bug Blocks: |
Description
Rolf Eike Beer
2023-09-17 17:36:13 UTC
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=54a8e50fc436e9bc102444401c211e09c14d2314 commit 54a8e50fc436e9bc102444401c211e09c14d2314 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-02-06 07:34:58 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-02-06 07:34:58 +0000 app-admin/syslog-ng: drop 4.2.0, 4.4.0-r1 back to ~arch Newer versions are buggy and may log broken PIDs in some cases. Bug: https://bugs.gentoo.org/914364 Signed-off-by: Sam James <sam@gentoo.org> app-admin/syslog-ng/syslog-ng-4.2.0.ebuild | 4 ++-- app-admin/syslog-ng/syslog-ng-4.4.0-r1.ebuild | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8c7dc635507f8bc00c9601630a0ffe5e2d004919 commit 8c7dc635507f8bc00c9601630a0ffe5e2d004919 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-02-06 07:33:58 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-02-06 07:33:58 +0000 Revert "app-admin/syslog-ng: drop 4.0.1, 4.1.1-r1, 4.1.1-r2" This reverts commit 808a63239296f90c10ba70820abfb1c55a8e4b25. Bug: https://bugs.gentoo.org/914364 Signed-off-by: Sam James <sam@gentoo.org> app-admin/syslog-ng/Manifest | 2 + app-admin/syslog-ng/syslog-ng-4.0.1.ebuild | 178 +++++++++++++++++++++++++ app-admin/syslog-ng/syslog-ng-4.1.1-r1.ebuild | 183 ++++++++++++++++++++++++++ app-admin/syslog-ng/syslog-ng-4.1.1-r2.ebuild | 183 ++++++++++++++++++++++++++ app-admin/syslog-ng/syslog-ng-4.6.0.ebuild | 2 +- 5 files changed, 547 insertions(+), 1 deletion(-) 4.4.0 at least doesn't fix it, can you try 4.6.0? (In reply to Sam James from comment #2) > 4.4.0 at least doesn't fix it, can you try 4.6.0? Actually, I've been using 4.4.0-r1 for a while now on a bunch of servers without issues. I have not had any issues on any of my systems. Currently running 4.2.0 on all systems. Based on the report, it looks like the issue is on sparc64 architecture. Why is everyone else being forced to downgrade? This downgrade caused some problems for me because of stats_freq syntax Correct Syntax for 4.0.X: > stats(freq(43200)); Correct syntax for 4.2.X: > stats_freq(43200); When downgrading from 4.2.X to 4.0.X, syslog-ng won't start > * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...[2024-02-06T14:55:01.257365] WARNING: Configuration file format is newer than the current version, please specify the current version number (4.0) in the @version directive. syslog-ng will operate at its highest supported version in this mode; config-version='4.2' > [2024-02-06T14:55:01.261382] WARNING: Your configuration file uses an obsoleted keyword, please update your configuration; keyword='stats', change='stats_freq', location='/etc/syslog-ng/syslog-ng.conf:16:2' > Error parsing options statement, syntax error, unexpected LL_IDENTIFIER, expecting LL_NUMBER in /etc/syslog-ng/syslog-ng.conf:16:8-16:12: > 11 > 12 # The default action of syslog-ng is to log a STATS line > 13 # to the file every 10 minutes. That's pretty ugly after a while. > 14 # Change it to every 12 hours so you get a nice daily update of > 15 # how many messages syslog-ng missed (0). > 16----> stats(freq(43200)); > 16----> ^^^^ > 17 # The default action of syslog-ng is to log a MARK line > 18 # to the file every 20 minutes. That's seems high for most > 19 # people so turn it down to once an hour. Set it to zero > 20 # if you don't want the functionality at all. > 21 mark_freq(3600); So I had to manually fix the config file to old 4.0.X syntax. Argh the other way around: Correct Syntax for 4.4.X: > stats(freq(43200)); Correct syntax for 4.0.X: > stats_freq(43200); I have confirmed that PID logging has been fixed in version app-admin/syslog-ng-4.6.0 on x86 architecture. (In reply to J. Roeleveld from comment #4) > Based on the report, it looks like the issue is on sparc64 architecture. > Why is everyone else being forced to downgrade? The upstream report is not exclusive to sparc64, it happened on arm too. (In reply to Robert Gill from comment #7) > I have confirmed that PID logging has been fixed in version > app-admin/syslog-ng-4.6.0 on x86 architecture. Let's try 4.6.0 as a stable target then? (In reply to Sam James from comment #8) > (In reply to J. Roeleveld from comment #4) > > Based on the report, it looks like the issue is on sparc64 architecture. > > Why is everyone else being forced to downgrade? > > The upstream report is not exclusive to sparc64, it happened on arm too. I can't see a link to the upstream report. I use amd64 and have not had anything resembling this issue. Masking amd64 when it's not affected is overkill (In reply to Sam James from comment #9) > (In reply to Robert Gill from comment #7) > > I have confirmed that PID logging has been fixed in version > > app-admin/syslog-ng-4.6.0 on x86 architecture. > > Let's try 4.6.0 as a stable target then? https://bugs.gentoo.org/924000 Right, I forgot that the previous stable target was syslog-ng-4.4.0-r1 and not 4.4.0-r2 which added grpc dep which is missing KW and thus syslog-ng-4.6.0 cannot be stabilized right away. (In reply to J. Roeleveld from comment #10) See the 'See Also' link to https://github.com/syslog-ng/syslog-ng/issues/4597. The bug might only affect 32-bit arches but there's nothing which guarantees that. (In reply to Sam James from comment #13) > (In reply to J. Roeleveld from comment #10) > > See the 'See Also' link to > https://github.com/syslog-ng/syslog-ng/issues/4597. > > The bug might only affect 32-bit arches but there's nothing which guarantees > that. ... and https://github.com/syslog-ng/syslog-ng/issues/4597#issuecomment-1868339588 explicitly says it's not 32-bit only. Thanks. (In reply to J. Roeleveld from comment #10) > (In reply to Sam James from comment #8) > > (In reply to J. Roeleveld from comment #4) > > > Based on the report, it looks like the issue is on sparc64 architecture. > > > Why is everyone else being forced to downgrade? > > > > The upstream report is not exclusive to sparc64, it happened on arm too. > > I can't see a link to the upstream report. > > I use amd64 and have not had anything resembling this issue. > Masking amd64 when it's not affected is overkill There is always a possibility to override the downgrade by using package.accept_keywords. Sam is trying to help here and version 4.6.0 is already being stabilized. |