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
Same here. Also get this in auth.log:
May 31 10:26:01 server CRON[18212]: PAM unable to
dlopen(/lib/security/pam_env.so): /lib/libpam.so.0: version
`LIBPAM_MODUTIL_1.1.3' not found (required by /lib/security/pam_env.so)
May 31 10:26:01 server CRON[18212]: PAM adding faulty module:
For the moment I performed:
apt-cache policy libpam-modules
which provided data about which old versions are available on my system.
So that I could run
apt-get install libpam-modules=1.1.1-2ubuntu2
rolling back from 1.1.1-2ubuntu5.2 to 1.1.1-2ubuntu2
in my case on the Lucid System.
--
You
Simply restarting the cron daemon should be sufficient.
I am preparing updated pam packages to fix this issue.
** Changed in: pam (Ubuntu)
Status: New = Confirmed
** Changed in: pam (Ubuntu)
Assignee: (unassigned) = Marc Deslauriers (mdeslaur)
** Changed in: pam (Ubuntu)
Just to confirm that restarting cron was enough for us as well, affects
at least 10.04 and 10.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790538
Title:
cron gives Module is unknown in syslog,
Restarting cron solved the issue for me too (10.04).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790538
Title:
cron gives Module is unknown in syslog, stops working
--
ubuntu-bugs mailing list
Yup. That does the trick. Thanks a lot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790538
Title:
cron gives Module is unknown in syslog, stops working
--
ubuntu-bugs mailing list
This hit us too on 10.04.2 . restarting cron seems to have fixed
things...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790538
Title:
cron gives Module is unknown in syslog, stops working
--
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
Again a bug that shouldn't happen. I had very bad bugs with apparmor and
kvm and now this. I'm very sad about the quality of ubuntu and I'm now
thinking to switch back to Debian (60 machines).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: pam (Ubuntu)
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790538
Title:
pam update causes cron to stop working with Module is unknown error
--
I have removed the affected versions from
{hardy,lucid,maverick,natty}-{security,updates} (pending the next
publisher run). Our sysadmins are going to block downloads of those
versions to try to minimise further problems.
--
You received this bug notification because you are a member of Ubuntu
12 matches
Mail list logo
