Results 1 to 3 of 3

Thread: Installation of new kernel does not write to /var/run/reboot-required on Intel x64

  1. #1
    Join Date
    Aug 2020
    Location
    Denmark
    Beans
    100
    Distro
    Ubuntu 22.04 Jammy Jellyfish

    Question Installation of new kernel does not write to /var/run/reboot-required on Intel x64

    I have Ubuntu Server 22.04 installed on both an Intel Atom (amd64) and a Raspberry Pi (arm64).

    With the last kernel update (installed by `unattended-upgrades`) the files `/var/run/reboot-required` and `/var/run/reboot-required.pkgs` have not been created on the Intel system (and thus the system is not flagged for reboot), but on the RasPi this works as expected.

    Here are the excerpts from `/var/log/apt/history.log`.

    Intel Atom:

    Code:
        Start-Date: 2022-05-24  06:52:55
        Commandline: /usr/bin/unattended-upgrade
        Install: linux-image-5.15.0-33-generic:amd64 (5.15.0-33.34, automatic), linux-headers-5.15.0-33-generic:amd64 (5.15.0-33.34, automatic), linux-modules-5.15.0-33-generic:amd64 (5.15.0-33.34, automatic), linux-headers-5.15.0-33:amd64 (5.15.0-33.34, automatic), linux-modules-extra-5.15.0-33-generic:amd64 (5.15.0-33.34, automatic)
        Upgrade: linux-headers-generic:amd64 (5.15.0.30.33, 5.15.0.33.36), linux-generic:amd64 (5.15.0.30.33, 5.15.0.33.36), linux-image-generic:amd64 (5.15.0.30.33, 5.15.0.33.36)
        End-Date: 2022-05-24  06:53:41
    Raspberry Pi:

    Code:
        Start-Date: 2022-05-25  06:44:33
        Commandline: /usr/bin/unattended-upgrade
        Install: linux-modules-5.15.0-1008-raspi:arm64 (5.15.0-1008.8, automatic), linux-raspi-headers-5.15.0-1008:arm64 (5.15.0-1008.8, automatic), linux-image-5.15.0-1008-raspi:arm64 (5.15.0-1008.8, automatic), linux-headers-5.15.0-1008-raspi:arm64 (5.15.0-1008.8, automatic)
        Upgrade: linux-headers-raspi:arm64 (5.15.0.1006.6, 5.15.0.1008.8), linux-raspi:arm64 (5.15.0.1006.6, 5.15.0.1008.8), linux-image-raspi:arm64 (5.15.0.1006.6, 5.15.0.1008.8)
        End-Date: 2022-05-25  06:46:44
    Test of files `/var/run/reboot-required` and `/var/run/reboot-required.pkgs`.

    Intel Atom:

    Code:
        $ cat /var/run/reboot-required
        cat: /var/run/reboot-required: No such file or directory
        
        $ cat /var/run/reboot-required.pkgs
        cat: /var/run/reboot-required.pkgs: No such file or directory
    Raspberry Pi:

    Code:
        $ cat /var/run/reboot-required
        *** System restart required ***
        
        $ cat /var/run/reboot-required.pkgs
        linux-image-5.15.0-1008-raspi
        linux-base
    I have the package `update-notifier-common` installed on both systems (was an existing solution on Ask Ubuntu). And yes, the symlink `/run -> /var/run` also exist.

    Both systems have been upgraded from 20.04, and here it worked as expected on both systems. It should also be noted that for other packages (like `libssl3`), I'm pretty sure the `/var/run/reboot-required` was updated on both systems.

    This is a little annoying for me because I use these files, both to be aware that a kernel update has been installed, and also to trigger a manual reboot at a designated time. So any suggestions on how to troubleshoot this and get the `/var/run/reboot-required` files to be written will be much appreciated.

    NB: I just got confirmation from a friend (also with an Intel server), and here the files have been written as expected. So it seems it's not a package bug either.
    Last edited by ameinild; May 25th, 2022 at 10:58 AM.
    Supermicro Server :: Atom C3558 (4) @ 2.2 GHz :: 64 GB ECC DDR4-2400 :: 512 GB NVMe :: 4x 2 TB SSD @ RAID-Z :: 1x Raspberry Pi 4 Server

    Scripts: directory-tools | rsync-backup | add-apt-key

  2. #2
    Join Date
    Sep 2011
    Location
    Behind you!
    Beans
    1,691
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Installation of new kernel does not write to /var/run/reboot-required on Intel x6

    Well, 1st thing I would check is what kernel your OS currently has loaded:
    Code:
    uname -r
    5.15.0-25-generic
    Then look in the look in /boot to see if there is a newer kernel.
    Code:
    ls -l /boot/vm*
    If the currently loaded kernel matches the latest one in /boot, then check if your system already rebooted:
    Code:
    uptime
    If the system did not reboot and is running the latest kernel, do you have a live patch running?

    LHammonds

  3. #3
    Join Date
    Aug 2020
    Location
    Denmark
    Beans
    100
    Distro
    Ubuntu 22.04 Jammy Jellyfish

    Re: Installation of new kernel does not write to /var/run/reboot-required on Intel x6

    I'm currently running 5.15.0-30-generic, and the latest installed is 5.15.0-33-generic. And the system has not rebooted since.

    However, the issue here isn't really whether or not the server has rebooted, or which kernel it's running.

    The exact problem is that the files /var/run/reboot-required and /var/run/reboot-required.pkgs remain non-existent, when they should have some content in them after a new kernel was installed.
    Supermicro Server :: Atom C3558 (4) @ 2.2 GHz :: 64 GB ECC DDR4-2400 :: 512 GB NVMe :: 4x 2 TB SSD @ RAID-Z :: 1x Raspberry Pi 4 Server

    Scripts: directory-tools | rsync-backup | add-apt-key

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •