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.

Description of problem:

We see this regularly on our systems when lansweeper's lsagent executes quick commands:

May 25 07:11:21 sudo[10105]:     root : TTY=unknown ; PWD=/opt/LansweeperAgent ; USER=root ; TSID=00000D ; COMMAND=/usr/sbin/dmidecode -t 1
May 25 07:11:21 systemd[1]: Started Session c4 of user root.
May 25 07:11:21 sudo[10105]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 25 07:11:21 sudo[10105]: pam_systemd(sudo:session): Failed to release session: Interrupted system call
May 25 07:11:21 sudo[10105]: pam_unix(sudo:session): session closed for user root
May 25 07:11:21 systemd[1]: session-c4.scope: Succeeded.

Version-Release number of selected component (if applicable):
systemd-239-74.el8_8.x86_64

How reproducible:
Regularly

Additional info:
It appears from https://github.com/systemd/systemd/issues/18817 that this may be fixed in 250.

And now it's gone away - it may only happen when sudo iologging is in effect?

Probably a duplicate of 2172846

*** This bug has been marked as a duplicate of bug 2172846 ***