unattended-upgrades hangs system on shutdown

[Bauldrick]

Binary package hint: unattended-upgrades

I am running Kubuntu-Netbook, based on Karmic I believe, my problem relates to shutting down the netbook.

version appears as: Installed 0.52ubuntu1

I'd expect the machine to shutdown, reboot when requested.

Instead it appears to shut down nicely until I see

*Shutting down ALSA [ OK ]
Checking for running unattended-upgrades:* Asking all remaining processess to terminate _

and it will just sit there, forever.

The unattended-upgrades script in /etc/init.d has been run on a seperate machine by hand and appears to hang on that machine also.

My bug reporting is not much up to scratch, so I hope I've covered it.

[Michael Vogt (mvo)]

Thanks for your bugreport.

Do you have more information on this? The syslog output maybe?

[Michael Vogt (mvo)]

I checked the code if nothing happens it should kill the update after a certain amount of time and it should also do logging via syslog.

[Janhaj (hajovsky-jan)]

Hi

I have Ubuntu Lucid Lynx and it is affected by this bug (for me). Default Kernel (without updates).

System does never shutdown.

[Hashim Khan (m-hashim-khan)]

Hi,

I am also running Lucid Lynx 10.04 and have the same problem. Its when the system shuts down or restarts -- it just hangs forever. Im not sure if this helps or not, since I'm a linux newbie, but I get this error message only when i have my USB devices (Logitech Z5 USB speakers, Samsung ML2010 printer, Logitech MX500 mouse and Western Digital 500GB external HD) attached to may computer when requesting a shutdown. If i unplug these devices, the shutdown/reboot process is fast and smooth as expected.

[Brian Dietz (dietz-brian-p)]

I am reporting that a IBM ThinkPad 390X I maintain with Lucid, and is current with updates; appears to be having similar issues. After selecting 'Shutdown...' this machine will get to the point of 'Checking for running unattended-upgrades:' and hang. I have to then hold the power button to shut the machine off. If I power back on, it reverts to the same state of 'Checking for running unattended-upgrades:'. I can only boot by removing battery and and AC plug and then replacing. Previously, this machine had Jaunty and worked fine this way before I did a fresh install of Lucid. Typically, this machine will not have a internet connection and not get updates until I bring home. See attached syslog

[Brian Dietz (dietz-brian-p)]

syslog file

[Joachim Haga (jobh)]

FWIW:

- It looks like this happens after kernel logging is turned off, so nothing in syslog

- From the code, it looks likely that one of these two is responsible:
       1) do_plymouth
       2) SysLogHandler

(Because: "in progress" is printed to console, so line 91 [logging.warning(...)] is reached; and the loop must hang somewhere since the timeout doesn't trigger. Does SysLogHandler perhaps wait for kernel logging (/dev/log) to come online again?)

[Ole Wolf (ole.wolf)]

After upgrading from Lucid netbook remix to Maverick on an MSI Wind U135 netbook, I'm seeing this bug, too. The bug also appeared after a fresh install of Maverick on the same netbook.

[Ole Wolf (ole.wolf)]

Trying to debug, it turns out it may not be the unattended upgrades shutdown check on my computer after all; it just happens to be at this stage where the "real" hang occurs. Specifically, the wireless network card seems to be the culprit, not the unattended upgrades script.

[tx (372046933-qq)]

The problem affects me too

[Hns (hanspeter-mls)]

Affected by problem after upgrading from Lucid netbook remix to Maverick.

[Whinis (john-p-turner)]

I too am now affected by this bug, 5 lines before the Checking for unattended-upgrades it says stopping bootlogd and then the line right before the upgrades line is stopping bluetooth. So it will not be logged.

[b1252666 (b1252666)]

Over here Lucid (no gui) also hangs on reboot with: "Checking for running unattended-upgrades: ".
Killing or terminating of "/usr/bin/dpkg --force-confdef --force-confold --status-fd 11 --unpack --auto-deconfigure /var/cache/apt/archives/libpam-modules_1.1.1-2ubuntu5.3_i386.deb" is impossible (tried 3 times).

> uname -a
Linux bs04 2.6.32-32-generic #62-Ubuntu SMP Wed Apr 20 21:54:21 UTC 2011 i686 GNU/Linux

> cat /proc/version_signature
Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16

Syslog lists as last 3 lines:
Jun 5 10:45:45 bs04 kernel: [55330.313035] ata6.15: failed to resume link (SControl FFFFFFFF)
Jun 5 10:45:45 bs04 kernel: Kernel logging (proc) stopped.
Jun 5 10:45:45 bs04 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1002" x-info="http://www.rsyslog.com"] exiting on signal 15.

[b1252666 (b1252666)]

Stopping other processes and daemons via webmin is still possible and sshd is still running.

Plugging a USB keyboard does not result in being able to type commands.

SSH reboot gives a response:
# reboot

Broadcast message from root@bs04
 (/dev/pts/0) at 11:13 ...

The system is going down for reboot NOW!

Though does not reboot. After SSH issueing: # reboot --force control is lost.

[b1252666 (b1252666)]

After reboot --force looses control, Webmin is still running:
> ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 Jun04 ? 00:00:00 /sbin/init
root 2 0 0 Jun04 ? 00:00:00 [kthreadd]
root 3 2 0 Jun04 ? 00:00:00 [migration/0]
root 4 2 0 Jun04 ? 00:00:12 [ksoftirqd/0]
root 5 2 0 Jun04 ? 00:00:00 [watchdog/0]
root 6 2 0 Jun04 ? 00:00:00 [migration/1]
root 7 2 0 Jun04 ? 00:00:00 [ksoftirqd/1]
root 8 2 0 Jun04 ? 00:00:00 [watchdog/1]
root 9 2 0 Jun04 ? 00:00:00 [events/0]
root 10 2 0 Jun04 ? 00:00:01 [events/1]
root 11 2 0 Jun04 ? 00:00:00 [cpuset]
root 12 2 0 Jun04 ? 00:00:00 [khelper]
root 13 2 0 Jun04 ? 00:00:00 [async/mgr]
root 14 2 0 Jun04 ? 00:00:00 [pm]
root 16 2 0 Jun04 ? 00:00:00 [sync_supers]
root 17 2 0 Jun04 ? 00:00:00 [bdi-default]
root 18 2 0 Jun04 ? 00:00:00 [kintegrityd/0]
root 19 2 0 Jun04 ? 00:00:00 [kintegrityd/1]
root 20 2 0 Jun04 ? 00:00:16 [kblockd/0]
root 21 2 0 Jun04 ? 00:00:17 [kblockd/1]
root 22 2 0 Jun04 ? 00:00:00 [kacpid]
root 23 2 0 Jun04 ? 00:00:00 [kacpi_notify]
root 24 2 0 Jun04 ? 00:00:00 [kacpi_hotplug]
root 25 2 0 Jun04 ? 00:00:00 [ata/0]
root 26 2 0 Jun04 ? 00:00:00 [ata/1]
root 27 2 0 Jun04 ? 00:00:00 [ata_aux]
root 28 2 0 Jun04 ? 00:00:00 [ksuspend_usbd]
root 29 2 0 Jun04 ? 00:00:00 [khubd]
root 30 2 0 Jun04 ? 00:00:00 [kseriod]
root 31 2 0 Jun04 ? 00:00:00 [kmmcd]
root 34 2 0 Jun04 ? 00:00:00 [khungtaskd]
root 35 2 0 Jun04 ? 00:00:11 [kswapd0]
root 36 2 0 Jun04 ? 00:00:00 [ksmd]
root 37 2 0 Jun04 ? 00:00:00 [aio/0]
root 38 2 0 Jun04 ? 00:00:00 [aio/1]
root 39 2 0 Jun04 ? 00:00:00 [ecryptfs-kthrea]
root 40 2 0 Jun04 ? 00:00:00 [crypto/0]
root 41 2 0 Jun04 ? 00:00:00 [crypto/1]
root 52 2 0 Jun04 ? 00:00:00 [scsi_eh_0]
root 53 2 0 Jun04 ? 00:00:00 [scsi_eh_1]
root 56 2 0 Jun04 ? 00:00:00 [scsi_eh_2]
root 57 2 0 Jun04 ? 00:00:00 [scsi_eh_3]
root 59 2 0 Jun04 ? 00:00:00 [kstriped]
root 60 2 0 Jun04 ? 00:00:00 [kmpathd/0]
root 61 2 0 Jun04 ? 00:00:00 [kmpathd/1]
root 62 2 0 Jun04 ? 00:00:00 [kmpath_handlerd]
root 63 2 0 Jun04 ? 00:00:00 [ksnapd]
root 64 2 0 Jun04 ? 00:00:11 [kondemand/0]
root 65 2 0 Jun04 ? 00:00:11 [kondemand/1]
root 66 2 0 Jun04 ? 00:00:00 [kconservative/0]
root 67 2 0 Jun04 ? 00:00:00 [kconservative/1]
root 238 ...

[Michel Menin (msmenin)]

This bug also affects me on a computer that has been through a HD upgrade (from 80gb sata to 500gb sata), this seems like the only notable difference between the time when it worked and afterwards.

I cloned the previous hd to the new one and resized the partitons. After succesfully resizing and never succesfully booting i went ahead and installed Narty. Installation went smoothly and froze up at shutdown as described. The system never boots.

[doken (doken)]

I thot I was facing this too, but on 11.10. Turns out is was just logging stopping at that point.

I found that stopping network-manager (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/875959) allow shutdown/restart. Whether that is due to the wrong ethernet driver being used (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/779040) or not I don't know yet.

[Knickers Brown (metta-crawler)]

This might be the same issue that was fixed in Bug #1654600