Your message dated Tue, 9 Dec 2014 15:17:32 +0100
with message-id <[email protected]>
and subject line Re: Bug#770448: reassigning to dpkg ("Setting up
libpam-modules-bin (1.1.8-3.1) hangs forever with dpkg using 100% cpu")
has caused the Debian Bug report #770448,
regarding Setting up libpam-modules-bin (1.1.8-3.1) hangs forever
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
770448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770448
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: libpam-modules-bin
version: 1.1.8-3.1
severity: important
x-debbugs-cc: [email protected]
User: [email protected]
Usertags: jenkins
https://jenkins.debian.net/view/d-i_manual/job/chroot-installation_wheezy_install_education-thin-client-server_upgrade_to_jessie/5/console
and
https://jenkins.debian.net/view/d-i_manual/job/chroot-installation_wheezy_install_education-workstation_upgrade_to_jessie/5/console
(and several attempts before) hang "forever" at
Preparing to unpack .../libpam-modules-bin_1.1.8-3.1_amd64.deb ...
Unpacking libpam-modules-bin (1.1.8-3.1) over (1.1.3-7.1) ...
Replacing files in old package libpam-modules:amd64 (1.1.3-7.1) ...
Setting up libpam-modules-bin (1.1.8-3.1) ...
I don't see any useful hint whats happening when looking at the processes:
29258 ? S 0:00 \_ /bin/sh -xe /tmp/hudson8147454957601885791.sh
29272 ? S 0:00 | \_ /bin/bash
/srv/jenkins/bin/chroot-installation.sh wheezy education-thin-client-server
jessie
29308 ? S 0:00 | \_ /usr/bin/python
/srv/jenkins/bin/setsid.py /tmp/jenkins-script-ObHlitjD wheezy
education-thin-client-server jessie
29325 ? Ss 0:00 | \_ /bin/bash
/tmp/jenkins-script-ObHlitjD wheezy education-thin-client-server jessie
39022 ? S 0:00 | \_ sudo chroot
/chroots/chroot-installation-wheezy.yru9xUhsR /tmp/tmp.7L3G0jVHmA
39023 ? S 0:00 | \_ /bin/sh
/tmp/tmp.7L3G0jVHmA
12963 ? S 0:08 | \_ apt-get -yf
dist-upgrade
57306 ? R 124:55 | \_ /usr/bin/dpkg
--status-fd 17 --unpack --auto-deconfigure
/var/cache/apt/archives/libpam-modules_1.1.8-3.1_amd64.deb
/proc is mounted inside the chroot but nothing else:
root@jenkins:~# mount|grep chroot-installation-wheezy.yru9xUhsR
/proc on /srv/workspace/chroots/chroot-installation-wheezy.yru9xUhsR/proc type
proc (rw,relatime)
binfmt_misc on
/srv/workspace/chroots/chroot-installation-wheezy.yru9xUhsR/proc/sys/fs/binfmt_misc
type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
root@jenkins:~#
(I'm using plain /usr/sbin/chroot here, not /usr/bin/schroot.)
OTOH,
https://piuparts.debian.org/wheezy2jessie/pass/libpam-modules-bin_1.1.8-3.1.log
does the upgrade just fine, so maybe this bug should only be of severity
"important",
filing as such, please upgrade the severity if you think thats appropriate.
Thanks for maintaining pam!
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 1.17.22
On Sun, 2014-12-07 at 13:43:36 +0100, Niels Thykier wrote:
> On 2014-12-07 12:50, Holger Levsen wrote:
> > control: severity -1 serious
> > control: reassign -1 dpkg
> > reassigning to dpkg, as this is the hanging process here. Several people
> > have
> > now reported they have seen this issue on there systems... (here and also
> > via
> > irc.)
> >
> > If you disagree please reassign to upgrade-reports, not qa.debian.org.
> For reference, dpkg is upgraded to 1.17.21 before the problem occurs.
>
> It is possible that this is fixed in dpkg 1.17.22 (which is not in Jessie).
I've confirmed now on Christian Grothoff's box that this was fixed in
dpkg 1.17.22, with commit 9a9ba74915876449b1fe20d4b76ab759f7d09d86
for #768852.
(Thanks Christian for the access, it was a very helpful and quick way
to reproduce this, instead of having to download GiBs of data over the
net, and wait hours for the thing to install and upgrade. I've only
fixed the immediate apt issue and gotten dpkg 1.17.22 installed, w/o
doing the full dist-upgrade, I've cleaned after myself, and you can
remove my access now, thanks again!)
Regards,
Guillem
--- End Message ---
