Bug 2210317

Summary:	pam_systemd(sudo:session): Failed to release session: Interrupted system call
Product:	Red Hat Enterprise Linux 8	Reporter:	Orion Poplawski <orion>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.8	CC:	systemd-maint-list
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-29 12:33:36 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:

Description Orion Poplawski 2023-05-26 15:01:17 UTC

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.

Comment 1 Orion Poplawski 2023-05-26 19:58:20 UTC

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

Comment 2 Lukáš Nykrýn 2023-05-29 12:33:36 UTC

Probably a duplicate of 2172846

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