| Summary: | app-admin/rsyslog: Block >=sys-apps/util-linux-2.26 due to new RFC5424 default format | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Deutschmann (RETIRED) <whissi> |
| Component: | [OLD] Server | Assignee: | Ultrabug <ultrabug> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | critical | CC: | mr_bones_, systemd |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=542368 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Thomas Deutschmann (RETIRED)
2015-03-05 23:21:41 UTC
CC'ing Michael Sterrett (app-admin/syslog-ng maintainer) CC'ing systemd team so they can verify if journald is also affected (seems like the current systemd version in tree is lacking of RFC5424 support) (In reply to Thomas D. from comment #2) > CC'ing systemd team so they can verify if journald is also affected (seems > like the current systemd version in tree is lacking of RFC5424 support) systemd-journald only supports ingestion of local syslog messages (/dev/log), so I don't see how a change to a format that is only used when sending messages over the network would be relevant. Every application using "logger" to log will log in new RFC5424 format. So if systemd is listening in /dev/log, journald will receive syslog messages in RFC5424 format. If systemd don't know the format, you will log at least garbage... (In reply to Thomas D. from comment #4) > Every application using "logger" to log will log in new RFC5424 format. > So if systemd is listening in /dev/log, journald will receive syslog > messages in RFC5424 format. If systemd don't know the format, you will log > at least garbage... According to the manual page, logger just calls syslog(3) by default. Running "logger foobar" works just fine here with util-linux-2.26; I see "logger[28971]: foobar" in my journal. Can you provide a simple way to reproduce this issue? Your test is valid BUT: 1) See the following acknowledged bugs in util-linux-2.26: - https://github.com/karelzak/util-linux/issues/163 - https://github.com/karelzak/util-linux/issues/161 - https://github.com/karelzak/util-linux/issues/159 - https://github.com/karelzak/util-linux/issues/157 2) Your syslog configuration is important: If you are only interested in the message itself you will probably don't hit any problems. But if you are interested in all the other information/details you will notice missing/invalid data. I was told that the best thing to test across different implementations is to use a JSON-based output. If for example systemd can handle RFC5424 format, all fields should be populated with the right values. If not, you will see empty/missing fields or empty/invalid values. (In reply to Thomas D. from comment #6) Thanks, the JSON suggestion is a good one. Let's continue this conversation on bug 542368 if you don't mind. As posted in bug 542368#3: We should add a general block for =sys-apps/util-linu-2.26. This will solve any problems logger from util-linux-2.26 is causing for any syslogger due to the changed default format. util-linux-2.26.1 should be released soon which will revert these changes. The new behavior will be the behavior from <util-linux-2.26. The changes are already present in util-linux git master (can be tested via =sys-apps/util-linu-9999). For more details please see bug 542368 comment #3. Closing, sys-apps/util-linux-2.26.1 which includes all the fixes is now available and in tree. |