FS#75776 - [glibc] 2.36-3 breaks message formatting in syslog() calls
Attached to Project:
Arch Linux
Opened by Mike Kazantsev (mk-fg) - Friday, 02 September 2022, 17:37 GMT
Last edited by freswa (frederik) - Tuesday, 06 September 2022, 21:55 GMT
Opened by Mike Kazantsev (mk-fg) - Friday, 02 September 2022, 17:37 GMT
Last edited by freswa (frederik) - Tuesday, 06 September 2022, 21:55 GMT
|
Details
Description:
glibc 2.36 includes a rewrite of misc/syslog.c which adds an extra space after timestamp when formatting message with syslog()/vsyslog() calls. This breaks rsyslogd and can potentially affect other syslog-processing software. Additional info: * glibc-2.36-3, while glibc-2.35-6 does not have this issue (note to anyone googling this: DO NOT downgrade glibc). * This issue is passed through systemd, and breaks rsyslogd, as reported here: https://github.com/rsyslog/rsyslog/issues/4979 * (Mis-)reported systemd issue about this, before realizing that bug is unrelated to it: https://github.com/systemd/systemd/issues/24540 Steps to reproduce: - On a safe-to-break VM with glibc-2.36, run following: (as root) `# strace -e sendto -s8000 -fp $(systemctl show -P MainPID dbus) 2>&1 | grep Activating` (in any other console/session) `timedatectl` - This will produce following strace output: `sendto(12, "<30>Sep 2 22:07:25 dbus-daemon[539]: ...` Two spaces before "dbus-daemon" is a bug, and doesn't conform to RFC, as noted by rsyslogd maintainer in https://github.com/rsyslog/rsyslog/issues/4979 - Rolling glibc back to 2.35 temporarily, running `systemctl restart dbus` and same commands above shows that issue is not present there. I haven't tested earlier 2.36 arch packages (if any), and assume that issue should be with upstream, as there were recent changes there. I was not able to report this on glibc bugtracker, as registrations for new accounts seem to be closed on it, though sent an email about it (as also suggested there), but haven't received anything back yet. Thanks! |
This task depends upon
Closed by freswa (frederik)
Tuesday, 06 September 2022, 21:55 GMT
Reason for closing: Fixed
Additional comments about closing: glibc-2.36-4 in [testing]
Tuesday, 06 September 2022, 21:55 GMT
Reason for closing: Fixed
Additional comments about closing: glibc-2.36-4 in [testing]
When you go to https://sourceware.org/bugzilla/createaccount.cgi which is suggested for "Reporting Bugs" on GNU Libc project, it asks for registration email to create account to report issues there, but entering it prints this in a big red box:
Because of spam user account creation has been restricted.
Contact your administrator or the maintainer (<hidden>@sourceware.org) for information about creating an account. Please mention the project you would like to create a bug for.
So I sent an email to indicated administrator address asking to create an account, with brief mention of the issue and same exact links above, just in case they'd need a reason for why I want to register there.
It probably looks like I meant a Mailing List posting, where follow-up discussion might be useful, but that's not the case, I think I'll likely either get a response with private bugzilla registration info or no response, if folks there are too busy, both of which shouldn't be relevant or useful here.