Bug 1059944

Summary:	sysstat cron job cause error message related to pam_systemd
Product:	[Fedora] Fedora	Reporter:	Yu Watanabe <watanabe.yu>
Component:	sysstat	Assignee:	Peter Schiffer <pschiffe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	pschiffe, varekova
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-21 08:58:33 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 Yu Watanabe 2014-01-31 02:44:55 UTC

Description of problem:

Not always, but frequently, sysstat crond job cause error such that

Jan 30 07:50:26 systemd[1]: Stopped Session 4224 of user root.
Jan 30 07:50:26 systemd[1]: Stopping Session 4224 of user root.
Jan 30 07:50:26 CROND[14856]: pam_systemd(crond:session): Failed to release session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy
Jan 30 07:50:01 CROND[14858]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jan 30 07:50:01 systemd[1]: Started Session 4224 of user root.
Jan 30 07:50:01 systemd[1]: Starting Session 4224 of user root.

If the sysstat crond job is disabled, then such error messages are not shown.

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

sysstat-10.1.6-1.fc20.x86_64
cronie-1.4.11-4.fc20.x86_64

How reproducible:

When the sysstat crond job is enabled, that is default settings.

Comment 1 Yu Watanabe 2014-01-31 04:06:01 UTC

Sorry, the error message is cut on the previous post.
The full error message is 

pam_systemd(crond:session): Failed to release session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Comment 2 Peter Schiffer 2014-05-20 16:45:25 UTC

Yu,

do you still see this problem? Are you using some non-default pam authentication? I'm not able to reproduce the problem, so if you have anything in your mind what could help, let me know ;-)

Thanks,

peter

Comment 3 Yu Watanabe 2014-05-21 00:58:23 UTC

Peter,

No. Now it seems work fine.

I have disabled cron sysstat job for a couple of month, because the error message I report above occupied journalctl output. Yesterday, I remembered this bug post, and tried to re-enable the cron job. I do not find any error messages related to sysstat or crond this 8 hours on 8 our cluster nodes.

I did not change any pam authentication. If I can remember correctly, updated systemd packages have provided after I post this problem. I guess the error messages that I found are related to a systemd problem and it might be fixed already.

Thanks, 

Yu

Comment 4 Peter Schiffer 2014-05-21 08:58:33 UTC

Yu,

thank you for letting me know! I'm closing the bug as CURRENTRELEASE, but if stumble across this problem again, feel free to reopen it.

peter