unattended upgrades does not do anything
Dear fellow debian users,
this is about a debian stable (=jessie) system and it does not
upgrade unattended and I have no clue how to debug this:
It's configured for jessie repositories:
# egrep -v "(^[[:space:]]*[#;\\])|^[[:space:]]*$" sources.list
deb http://ftp.de.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb http://ftp.de.debian.org/debian/ jessie-updates main
unattended-upgrades is installed:
# dpkg -l unattended-upgrades |grep ii
ii unattended-upgrades 0.83.3.2+deb8u1 all automatic installation of security upgrades
To me the apt config files look fine:
# egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/apt/apt.conf.d/02periodic
Dir "/";
Dir::Cache "var/cache/apt/";
Dir::Cache::Archives "archives/";
APT::Periodic::Enable "1";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::Download-Upgradeable-Packages-Debdelta "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Periodic::Verbose "2";
# egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/apt/apt.conf.d/20auto-upgrades
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
For some reasons there is obviously some dublification but I
don't think this is a problem.
I don't really know what the Origins-Pattern should look like but
I cannot remember to have messed with them:
# egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/apt/apt.conf.d/50unattended-upgrades
Unattended-Upgrade::Origins-Pattern {
"origin=Debian,codename=${distro_codename},label=Debian-Security";
};
Unattended-Upgrade::Package-Blacklist {
};
Cron is installed...
# dpkg -l cron|grep ii
ii cron 3.0pl1-127+deb8u1 i386 process scheduling daemon
... and running:
# ps fax|grep "[c]ron"
1499 ? Ss 0:02 /usr/sbin/cron -f
to me the basic configuration looks fine:
# egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/default/cron
READ_ENV="yes"
# egrep -v "(^[[:space:]]*[#;/])|^[[:space:]]*$" /etc/default/anacron
ANACRON_RUN_ON_BATTERY_POWER=no
and the system is on corded power:
# acpi -a
Adapter 0: on-line
there are cron configuration files for apt:
# ls -l /etc/cron.daily/apt*
-rwxr-xr-x 1 root root 15333 Mär 2 2016 /etc/cron.daily/apt
-rwxr-xr-x 1 root root 15335 Aug 31 2015 /etc/cron.daily/apt~
-rwxr-xr-x 1 root root 15290 Feb 16 2015 /etc/cron.daily/apt.dpkg-old
-rwxr-xr-x 1 root root 314 Nov 5 2012 /etc/cron.daily/aptitude
The only change to the apt config file is:
# diff -Nur /etc/cron.daily/apt~ /etc/cron.daily/apt
--- /etc/cron.daily/apt~ 2015-08-31 15:51:57.063709255 +0200
+++ /etc/cron.daily/apt 2016-03-02 10:04:25.595379714 +0100
@@ -282,7 +282,7 @@
# (some code taken from cron-apt, thanks)
random_sleep()
{
- RandomSleep=1800
+ RandomSleep=18
eval $(apt-config shell RandomSleep APT::Periodic::RandomSleep)
if [ $RandomSleep -eq 0 ]; then
return
... because this maschine used to be up only for round about an
hour a day, but this is not true any more, the system is now up
long enough for it to caught some security upgrade:
# uptime
17:25:41 up 12 days, 22:06, 3 users, load average: 0,00, 0,02, 0,00
but there is not much of an activity lately:
# ls -Altr /var/log/unattended-upgrades/|tail
-rw-r--r-- 1 root root 191 Jul 27 2015 unattended-upgrades-dpkg_2015-07-27_10:50:00.414149.log.1.gz
-rw-r--r-- 1 root root 384 Jul 29 2015 unattended-upgrades-dpkg_2015-07-29_18:20:11.584658.log.1.gz
-rw-r--r-- 1 root root 995 Aug 1 2015 unattended-upgrades.log.1.gz
-rw-r--r-- 1 root root 0 Aug 1 2015 unattended-upgrades-dpkg_2015-07-08_19:46:46.479193.log
-rw-r--r-- 1 root root 0 Aug 1 2015 unattended-upgrades-dpkg_2015-07-27_10:50:00.414149.log
-rw-r--r-- 1 root root 0 Aug 1 2015 unattended-upgrades-dpkg_2015-07-29_18:20:11.584658.log
-rw-r--r-- 1 root root 1058 Aug 4 2015 unattended-upgrades-dpkg_2015-08-04_20:25:14.411794.log
-rw-r--r-- 1 root root 1418 Aug 7 2015 unattended-upgrades-dpkg_2015-08-07_11:27:50.855330.log
-rw-r--r-- 1 root root 540 Aug 19 2015 unattended-upgrades-dpkg_2015-08-19_10:53:36.820176.log
-rw-r--r-- 1 root root 9056 Mär 2 2016 unattended-upgrades.log
Does anybody have an idea how to investigate this and who to
enable unattended upgrades?
Thanks, Gregor
Reply to: