unattended-upgrades in jessie fails to install anything.

2015-07-12 06:50:24,929 INFO Initial blacklisted packages:
2015-07-12 06:50:24,930 INFO Initial whitelisted packages:
2015-07-12 06:50:24,930 INFO Starting unattended upgrades script
2015-07-12 06:50:24,931 INFO Allowed origins are: ['origin=Debian,codename=jessie,label=Debian-Security', 'origin=Debian,archive=stable,label=Debian', 'origin=Debian,archive=stable,label=Debian-Security', 'origin=Debian,archive=testing,label=Debian', 'origin=Debian,archive=testing,label=Debian-Security']
2015-07-12 06:50:34,280 INFO Packages that will be upgraded: bind9-host host libbind9-90 libdns100 libisc95 libisccc90 libisccfg90 liblwres90
2015-07-12 06:50:34,281 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
2015-07-12 06:50:34,464 ERROR Installing the upgrades failed!
2015-07-12 06:50:34,465 ERROR error message: 'installArchives() failed'
2015-07-12 06:50:34,465 ERROR dpkg returned a error! See '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' for details

Log started: 2015-07-12  06:50:34
Error in function:
Log ended: 2015-07-12  06:50:34

Bastian

Thanks for your bugreport.

The erorr message looks like something in python-apt goes wrong (or in
the way u-u interacts with python-apt). Do you get a more meaningful
error message if you run:
  # unattended-upgrades --debug
on a terminal?

Is there anything "unusual" about the system? What apt/python-apt
version are in use?

Thanks,
 Michael

Hi Michael

For some reason this problem seems to only show if unattended-upgrades
is called by cron.  I've primed one machine with an extra debug flag.  I
see at least six machines exhibiting this behaviour.

I don't see anything unusual about this systems.

ii  apt                    1.0.9.8      amd64        commandline package manager
ii  apt-utils              1.0.9.8      amd64        package management related utility programs
ii  libapt-inst1.5:amd64   1.0.9.8      amd64        deb package format runtime library
ii  libapt-pkg4.12:amd64   1.0.9.8      amd64        package management runtime library
ii  python-apt             0.9.3.11     amd64        Python interface to libapt-pkg
ii  python-apt-common      0.9.3.11     all          Python interface to libapt-pkg (locales)
ii  python3-apt            0.9.3.11     amd64        Python 3 interface to libapt-pkg

ii  python                     2.7.9-1      amd64        interactive high-level object-oriented language (default version)
ii  python-minimal             2.7.9-1      amd64        minimal subset of the Python language (default version)
ii  python2.7                  2.7.9-2      amd64        Interactive high-level object-oriented language (version 2.7)
ii  python2.7-minimal          2.7.9-2      amd64        Minimal subset of the Python language (version 2.7)
ii  python3                    3.4.2-2      amd64        interactive high-level object-oriented language (default python3 version)
ii  python3-apt                0.9.3.11     amd64        Python 3 interface to libapt-pkg
ii  python3-minimal            3.4.2-2      amd64        minimal subset of the Python language (default python3 version)
ii  python3.4                  3.4.2-1      amd64        Interactive high-level object-oriented language (version 3.4)
ii  python3.4-minimal          3.4.2-1      amd64        Minimal subset of the Python language (version 3.4)

Bastian

I'm out of ideas.  It works if I force the cron script to run it with
-d.  It works if I run it by hand.

But I still got a handfull of machines that does not work if untouched.

Bastian