RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1709741 - NetworkManager sends invalid SYSLOG_FACILITY values to the journal
Summary: NetworkManager sends invalid SYSLOG_FACILITY values to the journal
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Thomas Haller
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-14 08:50 UTC by Jan Synacek
Modified: 2020-11-14 06:26 UTC (History)
13 users (show)

Fixed In Version: NetworkManager-1.20.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1707175
Environment:
Last Closed: 2019-11-05 22:29:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3623 0 None None None 2019-11-05 22:29:56 UTC

Description Jan Synacek 2019-05-14 08:50:18 UTC 
+++ This bug was initially created as a clone of Bug #1707175 +++

Description of problem:

According to https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#SYSLOG_FACILITY= the SYSLOG_FACILITY value is supposed to be an integer "(formatted as decimal string)" (and usually in the range 0 to 23).  However, on some systems, we see different values e.g.

> sudo journalctl -m -o export | grep SYSLOG_FACILITY= | grep -v 'SYSLOG_FACILITY=[0-9]' | sort -u
SYSLOG_FACILITY=CORE
SYSLOG_FACILITY=DEVICE
SYSLOG_FACILITY=DHCP4
SYSLOG_FACILITY=DHCP6
SYSLOG_FACILITY=DNS
SYSLOG_FACILITY=RFKILL
SYSLOG_FACILITY=SETTINGS

Either journald should somehow sanitize/normalize the SYSLOG_FACILITY values, or the documentation should be updated to notify log viewers/parsers to expect invalid values.

This is causing problems for some log collectors: https://bugzilla.redhat.com/show_bug.cgi?id=1703904#c3

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Noriko Hosoi on 2019-05-08 01:38:50 CEST ---

Note: It'd be easy to use NetworkManager for reproducing the issue.  I got these non-digital string facility values in my testing.  All of them are from NetworkManager.
SYSLOG_FACILITY=AUDIT
SYSLOG_FACILITY=BT
SYSLOG_FACILITY=CORE
SYSLOG_FACILITY=DEVICE
SYSLOG_FACILITY=DHCP4
SYSLOG_FACILITY=DHCP6
SYSLOG_FACILITY=DNS
SYSLOG_FACILITY=MB
SYSLOG_FACILITY=PLATFORM
SYSLOG_FACILITY=RFKILL
SYSLOG_FACILITY=SETTINGS
SYSLOG_FACILITY=SUPPLICANT
SYSLOG_FACILITY=WIFI

Please note that the issue is not observed on RHEL7 even though NetworkManager is launched.

--- Additional comment from Jan Synacek on 2019-05-14 09:47:26 CEST ---

From my testing and analysis of the logs, it's obvious it's the NetworkManager that sends string (sometimes multiple in one entry) SYSLOG_FACILITY values directly. The only way to do that that I'm aware of is to send a journal message via the journal API with such non-standard value. NetworkManager is the culprit and should be fixed.

As far as I know, journald is not a syslog daemon and is not interested in sanitizing invalid syslog fields. This should be documented in systemd.journal-fields.

--- Additional comment from Jan Synacek on 2019-05-14 10:48:10 CEST ---

https://github.com/systemd/systemd/pull/12559
Comment 1 Thomas Haller 2019-05-14 11:17:07 UTC 
On review: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/147
Comment 2 Thomas Haller 2019-05-17 19:31:09 UTC 
Fixed on master. See https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/147
Comment 4 Vladimir Benes 2019-08-05 13:05:06 UTC 
I see just 
SYSLOG_FACILITY=3
SYSLOG_FACILITY=10

and bunch of different numbers

[root@wsfd-netdev34-vm-9 ~]# sudo journalctl -m -o export | grep SYSLOG_FACILITY= | grep -v 'SYSLOG_FACILITY=[0-9]' | sort -u
Binary file (standard input) matches
Comment 6 errata-xmlrpc 2019-11-05 22:29:37 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3623
Note You need to log in before you can comment on or make changes to this bug.