Bug 433544

Summary:	PAM blocks munin and cacti cron jobs
Product:	[Fedora] Fedora	Reporter:	Johan Cwiklinski <fedora>
Component:	pam	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8	CC:	cra, ondrejj, thomas, vchepkov
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:	2008-02-20 07:59:09 UTC	Type:	---
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:	433835
Bug Blocks:

Description Johan Cwiklinski 2008-02-19 22:12:12 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; fr-FR; rv:1.9b4pre) Gecko/2008021510 Remi/3.0b4pre-0.beta3.20080215.fc8.remi Minefield/3.0b4pre

Description of problem:
Since updated to 0.99.8.1-17, munin and cacti cron jobs fail to run, with these messages from /var/log/cron:
Feb 19 20:00:01 odysseus crond[9900]: CRON (cacti): failed to open PAM security session: Module inconnu
Feb 19 20:01:01 odysseus crond[9937]: CRON (root): failed to open PAM security session: Module inconnu


Version-Release number of selected component (if applicable):
pam-0.99.8.1-17.fc8

How reproducible:
Always


Steps to Reproduce:
1. Update to pam-0.99.8.1-17.fc8
2. Wait 5 minutes to munin or cacti cronjobs to run
3. See the logs 

Actual Results:
cron jobs are not executed

Expected Results:
cron jobs should run successfull

Additional info:

Comment 1 Tomas Mraz 2008-02-20 07:25:21 UTC

'service crond restart' should help to eliminate this intermittent error.

Comment 2 Johan Cwiklinski 2008-02-20 07:59:09 UTC

Indeed, that solves the issue... 

Sorry, I should have tried this.

Comment 3 Tomas Mraz 2008-02-20 10:54:30 UTC

*** Bug 433608 has been marked as a duplicate of this bug. ***

Comment 4 Tomas Mraz 2008-02-21 17:07:53 UTC

*** Bug 433788 has been marked as a duplicate of this bug. ***

Comment 5 Charles R. Anderson 2008-02-21 17:13:25 UTC

Some more explanation on why this is impossible to fix would be helpful.  Should
a bug be filed against crond?

Thanks.

Comment 6 Tomas Mraz 2008-02-21 17:31:34 UTC

Pam probably could restart crond but it hardly can restart whatever other
daemons which can have loaded pam libraries. So the only possible fix for this
is just to reboot the machine. Or the administrator, who knows all the services
and daemons running on his machine, which loaded PAM library, can restart them.
This cannot be handled in any reasonably reliable and non-hackish way in the pam
package.

Comment 7 Tomas Mraz 2008-02-21 17:32:14 UTC

*** Bug 433835 has been marked as a duplicate of this bug. ***

Comment 8 Jan ONDREJ 2008-02-21 17:40:19 UTC

A solution can be to "do not release" new versions of pam in live of a fedora
distribution. New packages can go into fedora-devel, but not into stable updates.

After each upgrade an user must reboot it's machine to load new kernel and fix
also this problem.

Each update for stable update need to be compatible with older config files and
also binary compatible with applications, which can not be automatically
restarted. An user also can do automatic config update, if it is possible.

Comment 9 Tomas Mraz 2008-02-23 12:58:14 UTC

*** Bug 434615 has been marked as a duplicate of this bug. ***