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

Question

我运行Debian 7稳定与无人值守-升级(每天早上6点)，以确保我总是完全更新。我有以下配置：

$ 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 (e.g. 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. E.g. "user@example.com"
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";

如您所见，自动重新引导是正确的，因此服务器应该自动重新启动。上次我检查服务器的联机时间超过100天，这意味着从Debian 7.1到Debian 7.2的更新是在服务器运行时发生的(实际上，所有更新都已安装)，但这涉及内核更新，这意味着服务器应该重新启动。但事实并非如此。服务器运行得非常慢，所以我重新启动了修复程序。

我做了一些研究，发现无人值守的升级响应/var/run/中所需的重新引导文件。我触摸了这个文件，等待了一个星期，该文件仍然存在，并且服务器没有重新启动。所以我认为无人值守的高分忽略了自动重启部分。我是不是做错了什么？服务器为什么不重新启动？

顺便说一句，升级部分工作得很好，只是重新启动的部分似乎不像它应该的那样工作。

Answer 1

配置谈到的文件/var/run/reboot-required是由包update-notifier-common中的脚本创建的。如果没有安装此软件包，就不会发生自动重新启动。

不幸的是，在unattended-upgrades中没有提到这一点！