Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1866877

Summary:	The value of the 'PRIORITY' field has an unexpected length: 11 [v8.1911.0-3.el8]
Product:	Red Hat Enterprise Linux 8	Reporter:	Orion Poplawski <orion>
Component:	rsyslog	Assignee:	Attila Lakatos <alakatos>
Status:	CLOSED ERRATA	QA Contact:	Dalibor Pospíšil <dapospis>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	alakatos, dapospis, rsroka
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	rsyslog-8.2102.0-3.el8	Doc Type:	No Doc Update
Doc Text:	If this bug requires documentation, please select an appropriate Doc Type value.	Story Points:	---
Clone Of:
Clones:	1990738 (view as bug list)		Environment:
Last Closed:	2021-11-09 18:04:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1990738

Description Orion Poplawski 2020-08-06 17:11:29 UTC

Description of problem:

We are seeing the following:

Aug 05 23:05:25 HOSTNAME platform-python(mitogen:root@HOSTNAME:3983620)[3983661]: ansible-alternatives Invoked with name=modules.sh path=/usr/share/lmod/lmod/init/profile priority=50 link=None
Aug 05 23:05:25 HOSTNAME rsyslogd[2722]: The value of the 'PRIORITY' field has an unexpected length: 11  [v8.1911.0-3.el8]

Version-Release number of selected component (if applicable):
rsyslog-8.1911.0-3.el8.x86_64
systemd-239-30.el8_2.x86_64

It appears that something is parsing "priority=50" in the message and somehow trying to translate that into a logging priority?  I can't reproduce with a simple "logger priority=50".

Comment 1 Orion Poplawski 2020-08-06 17:16:56 UTC

This playbook seems to reproduce it well:

---
- hosts: localhost
  tasks:
    - name: "EL8: Use Lmod"
      alternatives:
        name: modules.sh
        path: /usr/share/lmod/lmod/init/profile
      become: yes

You would need to have Lmod installed from EPEL.

Comment 3 Attila Lakatos 2020-11-18 10:29:09 UTC

I could not reproduce the bug with the playbook you provided. Did you use the default rsyslog configuration file? If not, could you provide me your config?

Comment 4 Orion Poplawski 2020-11-18 15:56:44 UTC

The main rsyslog.conf file is the default, but we do configure forwarding:

/etc/rsyslog.d/forward.conf:

# Allow large messages
$MaxMessageSize 64k

# make gtls driver the default
$DefaultNetstreamDriver gtls

# certificate files
$DefaultNetstreamDriverCAFile /etc/pki/ca-trust/source/anchors/nwra.com_ipa_ca.crt
$DefaultNetstreamDriverCertFile /etc/pki/tls/certs/client.crt
$DefaultNetstreamDriverKeyFile /etc/pki/tls/private/client.key

$ActionSendStreamDriverAuthMode x509/name
$ActionSendStreamDriverPermittedPeer SERVER
$ActionSendStreamDriverMode 1 # run driver in TLS-only mode

$PreserveFQDN on

authpriv.*                              @@SERVER:6514;RSYSLOG_ForwardFormat

Comment 5 Attila Lakatos 2020-11-23 10:59:56 UTC

Have you experienced similar behavior on previous versions of RHEL? Or is this the first time?

I can see that you are using the old "legacy" rsyslog configuration format. I recommend to convert it to advanced format.

Comment 18 errata-xmlrpc 2021-11-09 18:04:45 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 (rsyslog and its related dependencies bug fix and enhancement update), 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-2021:4193