pam update causes cron to stop working with "Module is unknown" error
Bug #790538 reported by
Patric
This bug affects 76 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam (Ubuntu) |
Fix Released
|
Critical
|
Marc Deslauriers | ||
Hardy |
Fix Released
|
Critical
|
Unassigned | ||
Lucid |
Fix Released
|
Critical
|
Unassigned | ||
Maverick |
Fix Released
|
Critical
|
Unassigned | ||
Natty |
Fix Released
|
Critical
|
Unassigned |
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).
description: | updated |
Changed in pam (Ubuntu): | |
importance: | High → Critical |
summary: |
- cron gives "Module is unknown" in syslog, stops working + pam update causes cron to stop working with "Module is unknown" error |
Changed in pam (Ubuntu): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
I get the same message on 10.04 (Lucid) after running apt-get upgrade today. It pulled
bind9 bind9-host bind9utils dnsutils libbind9-60 libdns64 libisc60 libisccc60 libisccfg60 liblwres60 libpam-cracklib libpam-modules libpam-runtime libpam0g linux-libc-dev
The "Module is unknown" error starts to show up the minute the update has been completed.