无人值守升级不会重新启动

我使用无人值守升级(每天早上6点)运行Debian 7,以确保始终完全更新。 我有以下configuration:

$ cat /etc/apt/apt.conf.d/50unattended-upgrades // Automatically upgrade packages from these origin patterns Unattended-Upgrade::Origins-Pattern { // Archive or Suite based matching: // Note that this will silently match a different release after // migration to the specified archive (eg testing becomes the // new stable). "o=Debian,a=stable"; "o=Debian,a=stable-updates"; // "o=Debian,a=proposed-updates"; "origin=Debian,archive=stable,label=Debian-Security"; }; // List of packages to not update Unattended-Upgrade::Package-Blacklist { // "vim"; // "libc6"; // "libc6-dev"; // "libc6-i686"; }; // This option allows you to control if on a unclean dpkg exit // unattended-upgrades will automatically run // dpkg --force-confold --configure -a // The default is true, to ensure updates keep getting installed //Unattended-Upgrade::AutoFixInterruptedDpkg "false"; // Split the upgrade into the smallest possible chunks so that // they can be interrupted with SIGUSR1. This makes the upgrade // a bit slower but it has the benefit that shutdown while a upgrade // is running is possible (with a small delay) //Unattended-Upgrade::MinimalSteps "true"; // Install all unattended-upgrades when the machine is shuting down // instead of doing it in the background while the machine is running // This will (obviously) make shutdown slower //Unattended-Upgrade::InstallOnShutdown "true"; // Send email to this address for problems or packages upgrades // If empty or unset then no email is sent, make sure that you // have a working mail setup on your system. A package that provides // 'mailx' must be installed. Eg "[email protected]" Unattended-Upgrade::Mail "root"; // Set this value to "true" to get emails only on errors. Default // is to always send a mail if Unattended-Upgrade::Mail is set Unattended-Upgrade::MailOnlyOnError "true"; // Do automatic removal of new unused dependencies after the upgrade // (equivalent to apt-get autoremove) //Unattended-Upgrade::Remove-Unused-Dependencies "false"; // Automatically reboot *WITHOUT CONFIRMATION* if a // the file /var/run/reboot-required is found after the upgrade Unattended-Upgrade::Automatic-Reboot "true"; // Use apt bandwidth limit feature, this example limits the download // speed to 70kb/sec //Acquire::http::Dl-Limit "70"; 

正如你所看到的Automatic-Reboot是真的,因此服务器应该自动重启。 上次我查了一下服务器在线超过了100天,这意味着从服务器启动到Debian 7.2发生了更新(事实上,所有更新都已经安装),但是这涉及内核更新,这意味着服务器应该重新启动。 它没。 服务器运行速度非常慢,所以我重新启动了哪个固定的。

我做了一些调查,发现无人值守升级响应/ var / run /中需要重启的文件。 我碰到这个文件,等了一个星期,文件仍然存在,服务器没有重新启动。 所以我认为无人值守忽略了自动重启部分。 那么,我在这里做错了什么吗? 为什么服务器不能重新启动?

升级部分完美的顺便说一下,它只是重启的一部分,似乎不工作,因为它应该。

文件/var/run/reboot-required的configuration是由包update-notifier-common的脚本创build的。 没有安装这个软件包,不会自动重启。

不幸的是,这在unattended-upgrades任何地方都没有提及!