[Bug 790538] Re: pam update causes cron to stop working with "Module is unknown" error

[Peter Odding]

I appreciate that the problem has already been solved (I'm glad) but am
still considering whether to nominate this as the biggest fuck-up since
the Debian SSH/SSL key fiasco. If this truly affects every server Ubuntu
install out there using unattended upgrades (it affected my three
servers running Ubuntu 10.04 with unattended upgrades), this bug just
broke thousands of backup cron jobs all over the world and the worst
thing is it requires manual intervention from a sysadmin to get it going
again :-S.

-- 
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).