Package: schroot Version: 1.2.1-1 Severity: critical On goetz (our alpha buildd) the init script's start action hangs, causing the system to not boot up cleanly.
Since the init script is run in rcS/75, before there is an sshd or anything else useful this breaks the system completely, requiring remote hands from a local person if no OOB access is available. goetz:~# sh -x /etc/init.d/schroot start ... Recovering schroot sessions:+ return ++ /usr/bin/schroot --all-sessions --list --quiet + for chroot in '`$SCHROOT --all-sessions --list --quiet`' + /usr/bin/schroot --chroot=sid-alpha-sbuild-7855514e-e68e-40e3-8198-61366cd44074 --recover-session [just hangs here] It appears to be stuck in some kind of futex thing: wea...@goetz:~$ sudo strace -p 11214 2>&1 | head Process 11214 attached - interrupt to quit futex(0x120140158, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x120140158, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x120140158, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x120140158, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x120140158, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x120140158, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x120140158, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x120140158, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) futex(0x120140158, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable) wea...@goetz:~$ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
