8

In my /etc/apt/apt.conf.d/50unattended-upgrades i found this:

// Automatically reboot *WITHOUT CONFIRMATION*
//  if the file /var/run/reboot-required is found after the upgrade
//Unattended-Upgrade::Automatic-Reboot "false";

The issue is that I don't know what the default value is and so if I need to uncomment the line (I don't want my server to reboot btw).

Should I uncomment the line by safety? Are there further actions to perform after doing that?

elmattic
  • 183
  • You could test it be putting this file there manually as test sudo touch /car/run/reboot-required .. usually default should not be an autoreboot – derHugo Nov 05 '17 at 22:50

3 Answers3

6

The default for automatically rebooting after unattended-upgrades is FALSE.

You can confirm on your own system by looking where the default value is stored, in the script itself:

grep 'Automatic-Reboot"' /usr/bin/unattended-upgrade

The default could change with a software upgrade, although that seems unlikely. To be certain your systems don't reboot by after automatic upgrades, explicitly disable rebooting in your configuration.

Mark Stosberg
  • 3,327
5

If you don't want it to auto-reboot, make that section look like this:

// Automatically reboot *WITHOUT CONFIRMATION*
//  if the file /var/run/reboot-required is found after the upgrade 
Unattended-Upgrade::Automatic-Reboot "false";

I have it set that way and it works.

This page says that not rebooting is the default, but I'm pretty sure that's wrong. I think the first time my system autoinstalled a kernel (before I changed the config), it rebooted. But in either case, the config above will prevent it.

Organic Marble
  • 23,641
  • 15
  • 70
  • 122
  • Thanks, I'll take the safe path then. From what I understand only a kernel update needs a reboot and it is disable by default (if you have choosen auto install of security packages). Anyway I'll go the safe path. – elmattic Nov 05 '17 at 23:14
  • 8
    I don't think it's wrong, my systems don't reboot automatically unless I told them to. – Reinier Post Nov 14 '17 at 18:44
  • That could well be, I was experimenting with a lot of different options. – Organic Marble Nov 14 '17 at 19:15
  • 1
    100% with @ReinierPost - I have many servers in production; one rebooted automatically and the rest did not, which led me to this answer. All servers except the one that rebooted have it commented out thus using the default, which is to not reboot. The one that rebooted had it set to "true", which I have now fixed by commenting it out. – zaTricky Oct 03 '18 at 08:12
  • 1
    default value is to NOT reboot. https://libre-software.net/ubuntu-automatic-updates/ and https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/ Also, See https://serverfault.com/a/606852/399723 if you're using debian-7=wheezy or earlier AKA ubuntu 13.10 or earlier, because you'll need an additional package for this setting to work correctly. – SherylHohman Nov 12 '18 at 17:03
  • 1
    I made the same observation and was originally only looking at /etc/apt/apt.conf.d/50unattended-upgrades://Unattended-Upgrade::Automatic-Reboot "false"; . After 2 hours I realised I had: /etc/apt/apt.conf.d/10periodic:Unattended-Upgrade::Automatic-Reboot "true"; – Eleni Jul 15 '19 at 09:30
0

In my case I found that I had

Unattended-Upgrade::Automatic-Reboot "true"

in

/etc/apt/apt.conf.d/99custom-unattended-upgrades

I found it based on the hint by @Mark Stosberg, by running grep Reboot /etc/apt/apt.conf.d/*

See here for more details.

Zoltán
  • 776