Red Hat Bugzilla – Bug 433544
PAM blocks munin and cacti cron jobs
Last modified: 2008-08-02 19:40:36 EDT
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: CRON (cacti): failed to open PAM security session: Module inconnu
Feb 19 20:01:01 odysseus crond: CRON (root): failed to open PAM security session: Module inconnu
Version-Release number of selected component (if applicable):
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
cron jobs are not executed
cron jobs should run successfull
'service crond restart' should help to eliminate this intermittent error.
Indeed, that solves the issue...
Sorry, I should have tried this.
*** Bug 433608 has been marked as a duplicate of this bug. ***
*** Bug 433788 has been marked as a duplicate of this bug. ***
Some more explanation on why this is impossible to fix would be helpful. Should
a bug be filed against crond?
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
*** Bug 433835 has been marked as a duplicate of this bug. ***
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.
*** Bug 434615 has been marked as a duplicate of this bug. ***