package libpam-runtime 1.1.1-2ubuntu5 failed to install/upgrade:

[Pekka Hämäläinen]

- amd64 system
- upgrade from 8.04LTS to 10.04LTS, latest correction levels
- lsb_release -rd
    Description: Ubuntu 10.04.1 LTS
    Release: 10.04
- libpam-runtime 1.1.1-2ubuntu5

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: libpam-runtime 1.1.1-2ubuntu5
ProcVersionSignature: Ubuntu 2.6.24-28.79-generic
Uname: Linux 2.6.24-28-generic x86_64
NonfreeKernelModules: wlan_ccmp wlan_scan_sta fglrx ath_rate_sample ath_pci wlan ath_hal
Architecture: amd64
Date: Sun Sep 19 09:21:06 2010
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script returned error exit status 2
PackageArchitecture: all
SourcePackage: pam
Title: package libpam-runtime 1.1.1-2ubuntu5 failed to install/upgrade:

[Steve Langasek (vorlon)]

Thank you for taking the time to report this issue and help to improve Ubuntu.

The VarLogDistupgrade201009190834.gz logfile attached to your bug report is empty. Please attach /var/log/apt/term.log, which might show us something about how this package's upgrade is failing.

[Pekka Hämäläinen (pekka-hamalainen)]

On Sun, 2010-09-19 at 11:09 +0000, Steve Langasek wrote:
> Thank you for taking the time to report this issue and help to improve
> Ubuntu.
>
> The VarLogDistupgrade201009190834.gz logfile attached to your bug report
> is empty. Please attach /var/log/apt/term.log, which might show us
> something about how this package's upgrade is failing.
>
> ** Changed in: pam (Ubuntu)
> Status: New => Incomplete
>

[Pekka Hämäläinen (pekka-hamalainen)]

Ok, here is the /var/log/apt/term.log for today

Log started: 2010-09-19 07:41:32
(Reading database ... 141323 files and directories currently installed.)
Preparing to replace linux-image-2.6.24-28-generic 2.6.24-28.77 (using
.../linux-image-2.6.24-28-generic_2.6.24-28.79_amd64.deb) ...
Done.
Unpacking replacement linux-image-2.6.24-28-generic ...
Preparing to replace linux-headers-2.6.24-28 2.6.24-28.77 (using
.../linux-headers-2.6.24-28_2.6.24-28.79_all.deb) ...
Unpacking replacement linux-headers-2.6.24-28 ...
Preparing to replace linux-headers-2.6.24-28-generic 2.6.24-28.77 (using
.../linux-headers-2.6.24-28-generic_2.6.24-28.79_amd64.deb) ...
Unpacking replacement linux-headers-2.6.24-28-generic ...
Preparing to replace linux-libc-dev 2.6.24-28.77 (using
.../linux-libc-dev_2.6.24-28.79_amd64.deb) ...
Unpacking replacement linux-libc-dev ...
Setting up linux-image-2.6.24-28-generic (2.6.24-28.79) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.24-28-generic
Not updating initrd symbolic links since we are being
updated/reinstalled
(2.6.24-28.77 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.24-28.77 was configured last, according to dpkg)

Setting up linux-headers-2.6.24-28 (2.6.24-28.79) ...
Setting up linux-headers-2.6.24-28-generic (2.6.24-28.79) ...

Setting up linux-libc-dev (2.6.24-28.79) ...
Log ended: 2010-09-19 07:42:08

Timestamps in the log gives hint that those rows are not belonging to actual upgrade but related to latest correction updates of 8.04 - just before I tried the actual upgrade. Nevertheless, thats the latest one I can find.

Br Pekka

[Steve Langasek (vorlon)]

Unfortunately, without any logs, I don't think there's anything we're going to be able to do here. Please check that you have sufficient disk space on /var for logging to happen, and if the problem recurs, please open a new bug report.

[Pekka Hämäläinen (pekka-hamalainen)]

  Well, I have bug 560748 open as well. What I can tell is that there
exist plenty of hd space, and I can see the log generated in the console
screen, somehow that is not written to disc. So either the bug above
prevents the log being written or then I gave popped yet an another bug,
this time in update-manager and apt and their log reporting sub-system.
So, before dropping this libpam problem I would recommend that we try to
get the root causes visible. Thus I need some help how to get these logs
generated in first place.

On 2.10.2010 2:05, Steve Langasek wrote:
> Unfortunately, without any logs, I don't think there's anything we're
> going to be able to do here. Please check that you have sufficient disk
> space on /var for logging to happen, and if the problem recurs, please
> open a new bug report.
>
> ** Changed in: pam (Ubuntu)
> Status: Incomplete => Invalid
>

[Steve Langasek (vorlon)]

On Sat, Oct 02, 2010 at 03:09:48AM -0000, Pekka Hämäläinen wrote:
> So, before dropping this libpam problem I would recommend that we try to
> get the root causes visible. Thus I need some help how to get these logs
> generated in first place.

Please file a separate bug report on apt for this.

Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>