Unattended upgrade fails with segmentation fault in Ubuntu Server 10.10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
the python apt bindings |
Fix Released
|
Unknown
|
|||
python-apt (Debian) |
Unknown
|
Unknown
|
|||
python-apt (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Maverick |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[SRU for maverick]
* This bug makes unattended-upgrade completely unusable.
* This bug was fixed in upstream version 0.7.98.
* Just one-line backporting
https:/
TEST CASE:
1. Use out-of-date system which has security update notification
2. Run "$ sudo apt-get upgrade --download-only"
3. Run "$ sudo unattended-upgrade -d" and get Segmentation fault
4. Upgrade to -proposed package
5. Run "$ sudo unattended-upgrade -d" and all security updates get installed
-----
After upgrading from Ubuntu Server 10.04 to Ubuntu Server 10.10, I noticed that security updates were no longer being applied automatically (contrary to my configuration).
I did some poking around in the apt script (in etc/cron.daily). Here is the output with debug mode on. (I cleared out the time stamp files to force it to update now so errors regarding those are not important.)
power status (255) undetermined, continuing
system is on main power.
sleeping for 739 seconds
check_stamp: missing time stamp file: /var/lib/
apt-key net-update (success)
download updated metadata (success).
send dbus signal (success)
X11 connection rejected because of wrong authentication.
check_stamp: missing time stamp file: /var/lib/
download upgradable (success)
check_stamp: missing time stamp file: /var/lib/
Segmentation fault
unattended-upgrade (error)
check_stamp: missing time stamp file: /var/lib/
autoclean (success).
aged: ctime <30 and mtime <30 and ctime>2 and mtime>2
end remove by archive size: size=412396 < 512000
So, what's that seg fault in the middle there? Turns out it is the call to /usr/bin/
I can actually reproduce it like this:
$ sudo unattended-upgrade
Segmentation fault
Now, this is about all I know how to do to debug the issue. If you'd like me to run a stack trace or something on unattended-upgrade to figure out why it is crashing, please point me towards some directions to do so. (I notice that it is a python script and I am not very familiar with python.) In any case, this is a security issue, since security updates cannot be installed automatically, I have to remember to check the server often to make sure that security updates are applied.
visibility: | private → public |
description: | updated |
affects: | ubuntu → apt (Ubuntu) |
affects: | apt (Ubuntu) → unattended-upgrades (Ubuntu) |
description: | updated |
security vulnerability: | yes → no |
Changed in python-apt (Ubuntu): | |
status: | New → Confirmed |
Changed in python-apt: | |
status: | Unknown → Fix Released |
description: | updated |
tags: | added: i386 |
Changed in python-apt (Ubuntu Maverick): | |
milestone: | none → maverick-updates |
tags: | added: testcase |
Log information from /var/log/ unattended- upgrades. Whenever the unattended-upgrade script is launched, these three lines are logged (and no more):
2010-11-05 08:16:37,380 INFO Initial blacklisted packages: security' )"]
2010-11-05 08:16:37,382 INFO Starting unattended upgrades script
2010-11-05 08:16:37,382 INFO Allowed origins are: ["('Ubuntu', 'stable')", "('Ubuntu', 'maverick-
This can be used to tell about how far the script got before it crashed...