Ubuntu 20.04.1 LTS Server shutdown after 'unattended-upgrades.service: Succeeded.'

[david]

Hi,

We have a Ubuntu 20.04.1 LTS Server which seems to be shutting down after 'unattended-upgrades.service: Succeeded.' indication in logs.

The server mentioned: Dell PowerEdge R530

Based on my findings we noticed the following:

#/var/log/syslog:

Feb 2 02:30:50 systemd[1]: unattended-upgrades.service: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopping Session 1 of user sysadmin.
Feb 2 02:30:50 systemd[1]: Removed slice system-modprobe.slice.
Feb 2 02:30:50 systemd[1]: Stopped target Cloud-init target.
Feb 2 02:30:50 systemd[1]: Stopped target Graphical Interface.
Feb 2 02:30:50 systemd[1]: Stopped target Host and Network Name Lookups.
Feb 2 02:30:50 systemd[1]: Stopped target Timers.
Feb 2 02:30:50 systemd[1]: apt-daily-upgrade.timer: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Daily apt upgrade and clean activities.
Feb 2 02:30:50 systemd[1]: apt-daily.timer: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Daily apt download activities.
Feb 2 02:30:50 systemd[1]: e2scrub_all.timer: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems.
Feb 2 02:30:50 systemd[1]: fstrim.timer: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Discard unused blocks once a week.
Feb 2 02:30:50 systemd[1]: fwupd-refresh.timer: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Refresh fwupd metadata regularly.
Feb 2 02:30:50 systemd[1]: logrotate.timer: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Daily rotation of log files.
Feb 2 02:30:50 systemd[1]: man-db.timer: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Daily man-db regeneration.
Feb 2 02:30:50 systemd[1]: motd-news.timer: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Message of the Day.
Feb 2 02:30:50 systemd[1]: systemd-tmpfiles-clean.timer: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Feb 2 02:30:50 systemd[1]: Stopped target System Time Synchronized.
Feb 2 02:30:50 systemd[1]: Stopped target System Time Set.
Feb 2 02:30:50 systemd[1]: lvm2-lvmpolld.socket: Succeeded.
Feb 2 02:30:50 systemd[1]: Closed LVM2 poll daemon socket.
Feb 2 02:30:50 systemd[1]: systemd-rfkill.socket: Succeeded.
Feb 2 02:30:50 systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Feb 2 02:30:50 systemd[1]: Stopping Accounts Service...
Feb 2 02:30:50 systemd[1]: Stopping Availability of block devices...
Feb 2 02:30:50 systemd[1]: cloud-final.service: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Execute cloud user/final scripts.
Feb 2 02:30:50 systemd[1]: Stopped target Multi-User System.
Feb 2 02:30:50 systemd[1]: Stopped target Login Prompts.
Feb 2 02:30:50 systemd[1]: Stopped target ZFS startup target.
Feb 2 02:30:50 systemd[1]: Stopped target ZFS pool import target.
Feb 2 02:30:50 systemd[1]: Stopped target ZFS volumes are ready.
Feb 2 02:30:50 systemd[1]: Stopping LSB: automatic crash report generation...
Feb 2 02:30:50 systemd[1]: Stopping Deferred execution scheduler...
Feb 2 02:30:50 systemd[1]: cloud-config.service: Succeeded.
Feb 2 02:30:50 systemd[1]: Stopped Apply the settings specified in cloud-config.
Feb 2 02:30:50 systemd[1]: Stopped target Cloud-config availability.
Feb 2 02:30:50 blkdeactivate[36212]: Deactivating block devices:
Feb 2 02:30:50 systemd[1]: Stopped target Network is Online.
Feb 2 02:30:50 systemd[1]: Stopping Regular background program processing daemon...
Feb 2 02:30:50 systemd[1]: Stopping Create final runtime dir for shutdown pivot root...
Feb 2 02:30:50 systemd[1]: Stopping Getty on tty1...
Feb 2 02:30:50 systemd[1]: Stopping LSB: Record successful boot for GRUB...
Feb 2 02:30:50 systemd[1]: Stopping irqbalance daemon...
Feb 2 02:30:50 systemd[1]: Stopping LVM event activation on device 8:19...
Feb 2 02:30:50 systemd[1]: Stopping Dispatcher daemon for systemd-networkd...
Feb 2 02:30:50 systemd[1]: Stopping Authorization Manager...
Feb 2 08:12:53 systemd-sysctl[852]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Feb 2 08:12:53 systemd-sysctl[852]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists).

#/var/log/auth.log:
Feb 2 02:30:50 systemd-logind[1646]: Power key pressed.
Feb 2 02:30:50 systemd-logind[1646]: Powering Off...
Feb 2 02:30:50 systemd-logind[1646]: System is powering down.
Feb 2 02:30:50 sudo: pam_unix(sudo:session): session closed for user root
Feb 2 08:12:53 sshd[2006]: Server listening on 0.0.0.0 port .
Feb 2 08:12:53 sshd[2006]: Server listening on :: port .
Feb 2 08:12:53 systemd-logind[1992]: New seat seat0.
Feb 2 08:12:53 systemd-logind[1992]: Watching system buttons on /dev/input/event0 (Power Button)
Feb 2 08:12:53 systemd-logind[1992]: Watching system buttons on /dev/input/event1 (Avocent Keyboard/Mouse Fun

#last -x (the server time was changed, it was UTC - 2hrs ahead thus 04:31):
reboot system boot 5.4.0-65-generic Tue Feb 2 08:12 still running
shutdown system down 5.4.0-65-generic Tue Feb 2 04:31 - 08:12 (03:41)

I have also generated iDrac reports to check power button sensors and firmware with Dell Support - All hardware is operating normally.

The server is housed in a DC and confirmed no one was working on the server or fiddling around it at the time.

This has happened more than twice with log files indicating the same events.

I also checked log files for any other abnormalities.

Also done the following:

#Disabled the Power Button:
    Path = "/etc/systemd/logind.conf"
    Original Parameter = "#HandlePowerKey=poweroff"
    Updated Parameter = "HandlePowerKey=ignore"

I haven't done a 'systemctl restart systemd-logind' after change yesterday but have done so this morning (after last event).

Questions:

1. Is this a Bug?
2. What in Ubuntu OS could be initiating a reboot?
3. Any other measures that can be taken to further deep-dive?

Thanks in advance for your assistance.

Much Appreciated,
David

[prebenjaeger (prebenjaeger)]

Hi David. I'm experiencing pretty much the same issue, only once though. But odd enough for me to want to investigate it. Did you ever get an answer?