Reboot needed won't go away

[Randomz]

SYSTEM INFORMATION
OS type and version	Ubuntu Linux 24.04.5
Webmin version	2.670
Package updates	All installed packages are up to date

After some updates the system monitor Reboot Required triggered and rebooted the server however it was still saying that it needs a reboot.

I have since manually rebooted it twice and it still says it needs a reboot.

Reboot Required, Status history is showing red in both columns for each 5 minute check for the last 45 minutes.

[stefan1959]

Try package refresh or/and clear cache in the theme.

[Randomz]

3 reboots should have done the job, I have tried refresh as well.
The list of Red Status icons keeps growing ever 5 minutes.
Definitely a hiccup.

[stefan1959]

Maybe you can spot something in browser inspect.

[Randomz]

Not my job, I am not a coder.

I just report problems when I find them. I do test what I can before reporting .

[shoulders]

In Webmin 2.670 there was a fix for DNF systesm (i.e. no Ubuntu), I mention it just incase this change has broken it for Ubuntu system.

• Fix reboot-required detection on DNF systems without a standalone needs-restarting command forum.virtualmin.com/t/137973

Webmin 2.670 and Usermin 2.570 released

Howdy all, We’ve rolled out Webmin 2.670 and Usermin 2.570 to all Virtualmin repos. Changes since Webmin 2.660 and Usermin 2.560 Add new Hardware Information module for inspecting system, firmware, security, PCI, USB, storage, network, processor, sensor, driver, and kernel module details Add options to send Webmin and Usermin errors to the systemd journal forum.virtualmin.com/t/136562 Add webserver logging controls to Usermin Configuration module Add option to rotate Webmin and Usermin webse…

[Randomz]

This has gone the other way, from not showing reboot required, to not making it go away.

Hopefully this chatter doesn’t stop staff from seeing this thread.

[Randomz]

I may have found a related problem on another server, this one EL10 with Webmin 2.670.

The Reboot Required monitor correctly changed from green to red after a kernel update and sent the notification email.

I originally had the action set to:

shutdown -r +15 "Rebooting 15 minutes after kernel update"

The notification said:

Running shutdown -r +15 "Rebooting 15 minutes after kernel update" ..

but no reboot was scheduled (/run/systemd/shutdown/scheduled did not exist).

To eliminate the delayed shutdown as the problem, I restored a snapshot and repeated the update with the monitor action changed simply to:

/usr/sbin/reboot

At 00:20 the monitor changed from green to red and the notification said:

Running /usr/sbin/reboot ..

but the server did not reboot.

The package update continued for a while after that, but has now finished and the load has dropped. The server still has not rebooted. The Reboot Required monitor continues to add a red status entry every five minutes.

So this looks as though the Reboot Required monitor is detecting the condition and reporting that it is running the configured command, but the reboot command is not actually taking effect.

Just rebooted the EL10 server manually, the Reboot Required message goes away.