this seems to have reared its head again on ubuntu 8.04 (and gentoo!) as
part of an update on 11/june
--
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
Apart from crond, anacron seems had been hanged since may31 too, there
is an apt defunct process there, what should i do or is it require to
reboot?
root 22114 1 0 May31 ?00:00:00 /bin/sh -c test -x
/usr/sbin/anacron || ( cd / run-parts --report /etc/cron.daily )
root 22115
I'm not sure why those jobs would have hung. I would kill them and
restart the anacron daemon.
--
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
Any system has its weak spots. This incident is an illustration that
cron is such a weak spot and breakage can be devastating, and as Chris
wrote in #41, it is lucky that sshd did not break, or things would have
been a lot worse.
Offhand, I see two possible solutions:
* cron should be built
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
Bugs, which is subscribed to Ubuntu.
Jamie - thanks for the report - and thanks for the great product, and
thanks to all who take the heat when this happens - really appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790538
Update applied, seems okay.
--
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
--
ubuntu-bugs mailing list
For those who haven't restarted cron:
As expected, since cron is dead, unattended-upgrade does not start thus fix is
not being installed automatically.
apt-get update + upgrade does work and cron does not need a restart.
But it still means a manual intervention to fix the problem, great ... not
update + upgrade works (i.e. fixed cron) on 10.04 server LTS, on a cron
that had been broken, but NOT manually restarted.
--
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
I agree with Mike - relax and appreciate the fact that the solution was
quickly found and made available.
Yak
--
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
@ubuntu devs: Since this has the potential to break lots servers in
various nasty ways it might (?) be wise to post a heads up to a mailing
list that's (hopefully) followed by lots of sysadmins like ubuntu-
security-announce. I'm guessing there's a whole policy about what should
and should not be
Thanks for the fix. Much appreciated! :)
I noticed it because for some of my machines (I run Ubuntu 10.04, 11.04
and Debian 6) stopped sending logcheck reports. Only had the time to
look into it today, though. It wasn't as critical for me, though some of
the backups that landed on the staging
I would like to briefly follow up to let people know that regressions are
treated very seriously in Ubuntu. Regressions are closely examined to identify
areas of improvement going forward, and as such, we have created a public
incident report in:
Anyone doing unattended upgrades in production opens themselves up to
this sort of risk. Sure it was a screwup by Ubuntu, but would have been
easily resolved if you'd done upgrades in a scheduled maintenance
window. All aboard thye failboat.
--
You received this bug notification because you
Not all aspects of this PAM failure can be fixed easily, since daemons
other than cron were also affected. Cron can be restarted without user
impact, but something like xdm cannot be.
(Since we got hurt by the xdm issue, not by the cron issue, I am
rather sensitive about this.)
I personally
** Summary changed:
- cron gives Module is unknown in syslog, stops working
+ pam update causes cron to stop working with Module is unknown error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790538
Issued occurred upgrading to 1.1.1-2ubuntu5.2 on lucid. Restarting cron
solves the problem.
--
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
Colin, that seems like a horrible solution - you now have everybody's
apt claiming they need to get a package that 404s, causing apt-get
upgrade to fail. I understand a buggy package was released, but once
that has been done, you can't just remove the package itself (while
leaving reference to it
Fixed pam packages are being prepared, will go through QA, and will be
released in the next few hours.
--
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
Natty update manager says 'Failed to download package files' 'check Internet
connection'
these are the details
Failed to fetch
http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam0g_1.1.2-2ubuntu8.2_amd64.deb
404 Not Found [IP: 91.189.92.167 80]
Failed to fetch
This PAM issue also affects xdm, which no longer allows people to log in
(it syslogs the same error message). This has caused us serious problems
on our multiuser login servers, because of course we cannot simply
reboot the machines and restarting xdm has the pleasant side effect of
instantly
@Chris: in your situation, downgrading the package to the previous
version should work around the issue until we publish updated pam
packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790538
Vijay: we've gone over this at enormous length in the past, and settled
on this as standard process for sufficiently bad problems, on the
grounds that even though it does cause 404s it's better than the
breakage.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Vijay: and obviously this is only a temporary solution until a proper
fix is published, which indeed will go forward in version numbers.
--
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:
@Marc: the previous libpam version (1.1.1-2ubuntu5 for 10.04 LTS)
doesn't seem to be available any more, or at least 'apt-get' can't
find it, which makes downgrading hard. We would have to roll all the
way back to 1.1.1-2ubuntu2 ... which is missing a root escalation CVE
(CVE-2010-0832, root priv
Chris: If necessary, previous versions can always be downloaded manually
from Launchpad:
https://launchpad.net/ubuntu/lucid/+source/pam/1.1.1-2ubuntu5.1 and
follow the appropriate link under Builds. (Obviously not ideal but
may help as a stopgap.)
--
You received this bug notification because
Adding in the set of affected series, for tracking purposes.
** Also affects: pam (Ubuntu Hardy)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Natty)
Importance: Undecided
Just for the record: pulling the pam packages like this completely
breaks the network-based install I'm doing from an official Ubuntu
mirror, because of the 404-errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package pam - 1.1.2-2ubuntu8.3
---
pam (1.1.2-2ubuntu8.3) natty-security; urgency=low
* SECURITY REGRESSION:
- debian/patches/security-dropprivs.patch: updated patch to preserve
ABI and prevent daemons from needing to be restarted. (LP: #790538)
This bug was fixed in the package pam - 1.1.1-4ubuntu2.3
---
pam (1.1.1-4ubuntu2.3) maverick-security; urgency=low
* SECURITY REGRESSION:
- debian/patches/security-dropprivs.patch: updated patch to preserve
ABI and prevent daemons from needing to be restarted. (LP:
This bug was fixed in the package pam - 1.1.1-2ubuntu5.3
---
pam (1.1.1-2ubuntu5.3) lucid-security; urgency=low
* SECURITY REGRESSION:
- debian/patches/security-dropprivs.patch: updated patch to preserve
ABI and prevent daemons from needing to be restarted. (LP: #790538)
This bug was fixed in the package pam - 0.99.7.1-5ubuntu6.4
---
pam (0.99.7.1-5ubuntu6.4) hardy-security; urgency=low
* SECURITY REGRESSION:
- debian/patches/security-dropprivs.patch: updated patch to preserve
ABI and prevent daemons from needing to be restarted. (LP:
Paul: understood, and we knew it was a trade-off. It will be fixed very
soon.
--
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
** Branch linked: lp:ubuntu/natty-security/pam
** Branch linked: lp:ubuntu/maverick-security/pam
** Branch linked: lp:ubuntu/hardy-security/pam
** Branch linked: lp:ubuntu/lucid-security/pam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: pam (Ubuntu)
Status: Confirmed = Fix Released
--
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
@Marc: Thanks. All is well. People need to RELAX. S*#@ happens sometimes
and for this to pop up and be fixed so quickly is brilliant work from
the Ubuntu maintainers. Its a bit juvenile to expect perfection when it
exists nowhere else and especially because no one here paid for for
Ubuntu.
Thanks
I can confirm the bug.
I can confirm that restarting cron works.
I can confirm that after applying the newest pam related packages
updated 19 minutes ago cron is working as expected.
Not the best confirmation since I restarted cron prior to applying the
fix, but there you go.
Thank you
We have an Ubuntu 10.04 machine with the original update applied where
xdm had not been restarted and was thus rejecting login attempts.
I can confirm that applying the just-released PAM update made xdm
accept logins again. The update also did not break cron, which had been
restarted and so was
38 matches
Mail list logo
