[Bug 790538] Re: pam update causes cron to stop working with "Module is unknown" error
Cam Hutchison
cam at camh.ch
Thu Jun 2 12:27:22 UTC 2011
Chris - sshd kept working because it re-execs itself when doing auth.
This means it got the new libpam.so and was able to dlopen pam_env.so
without the symbol version mismatch.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/790538
Title:
pam update causes cron to stop working with "Module is unknown" error
Status in “pam” package in Ubuntu:
Fix Released
Status in “pam” source package in Lucid:
Fix Released
Status in “pam” source package in Maverick:
Fix Released
Status in “pam” source package in Natty:
Fix Released
Status in “pam” source package in Hardy:
Fix Released
Bug description:
Upgrading libpam-modules from 1.1.1-4ubuntu1 to 1.1.1-4ubuntu2.2, cron stopped working, just gives a log message "Module is unknown". This happened during unattended-upgrades this night, so there might be a lot of people who didn't realize that yet.
Downgrading to 1.1.1-4ubuntu1 fixes this.
Ubuntu 10.10 amd64, almost vanilla, fresh, minimum install + java (ppa) + postgresql9 (ppa).
More information about the foundations-bugs
mailing list