[Bug 790538] Re: cron gives "Module is unknown" in syslog, stops working

Hark ubuntu at komkommerkom.com
Tue May 31 11:47:48 UTC 2011


Restarting the cron daemon also worked for me. By the way I also had to
restart atd where I use it.

This must be one of the worst bugs in years on a LTS version. Just
imagine how many backup scripts won't run due to this bug. And it won't
be fixed automatically as the unattended-upgrades won't be started as
well...

-- 
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:
  cron gives "Module is unknown" in syslog, stops working

Status in “pam” package in Ubuntu:
  Confirmed

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