Is already set on 5 minutes but also on manual refresh I still see not up in the Dashboard but I see up under System and Server Status. I hope will work.
Thanks.
You may need to toggle the switch some times it does not save the setting
Thinking about this, security updates should be done sooner, not later.
I have changed scheduled checking to per hour, and then set the reboot to be +30 which gives me 30 minutes to see the mail that a reboot will occur.
With the speed of modern servers a reboot takes less than 30 seconds.
More thoughts about the reboot delay.
shutdown -r +15 has nasty side effect of only allowing priviledged users to login during that time - which isn’t clients.
So I switched to using atd, changed from:
/usr/sbin/shutdown -r +15 "Rebooting after kernel update" to
echo '/usr/sbin/shutdown -r now "Rebooting after kernel update"' | at now + 15 minutes
I have thought of having no delay at all but I noticed that the “need reboot” message can appear before all updates have been installed, so have now set mine down to 2 minutes.
This is pretty much what I have achieved now with tools already available in Webmin/Virtualmin.
I have simplified even more by using the command /usr/sbin/reboot and setting the schedule for /etc/webmin/package-updates/update.pl to be 3-5 minutes ahead of the 5 minute check for reboot to allow time for the update installation to finish.
In my view, reboots should be performed during a controlled maintenance window when an admin is around, rather than unattended overnight, since any failure could lead to prolonged downtime.
And yet it is uncommon for a kernel security update to justify an immediate, unscheduled reboot.
Yes, I personally would never reboot a server that I was not monitoring, especially when hosting client sites. It happens, for some reason or other the server does not come back up, or apache etc fails to start.
David
While I agree 100% this is about software flexibility and adoption. I worked for a company with a very high uptime guarantee. If I had to get up at 2AM to reboot a server, that’s what I did.
Previously I would always wait until late at night, down the server, do a snapshot, restart it and then apply the updates.
For EL 10, security updates are happening very fast, had 2 in less than 24 hours recently.
This thread also got me thinking that in all the years I have been running Linux servers, I have never had a problem with kernel related updates, only occasionally with non-security updates eg some from here.
With recent developments such as Claude Mythos 5 finding bugs everywhere, and bad actors racing to exploit new bugs faster than developers can plug them, my thoughts are that security updates are now very important.
So current method for me is to auto apply security updates and reboot if needed. Only 30 seconds downtime helped me make that decision.
I then manually apply non-security updates when it suits me and after I test them on a spare server.
I think this is a good discussion to be had at this time.
In any case unfortunately following the instruction on this topic never worked for me.
The server has a kerenel update since yesterday and the server was not restarted.
I will stay with this issue. Now let’s remove the monitor that was not working for me.
I will maybe try with a custom script.
Would be useful not only be able to schedule a reboot but also maybe choose only to be notified by email so.. if the admin never log in every day to Virtualmin control panel can know a manual reboot is necessary.
Currently the showed banner is view only if the admin log-in into Virtualmin. A notification of a required reboot can be useful.
Observation.
You need to have created the Reboot monitor at least 10 minutes before creating the Auto Software Update part.
This is because the reboot monitor - which checks every 5 minutes, has to record at least one “Normal” flag so that it can then detect the change to Needing Reboot.
If it was already saying "Reboot Needed, then it’s too late to create the Reboot monitor as it only detects the change from not needed to needed.
The monitor was created different hours ago so just was not working.
Now I will try with a custom script, for now I decided two email alert on two days when a reboot is needed and the third time the reboot if not done will be run automatically.
I will see if this will work.
I get an email when my server requires a reboot after setting up a reboot monitor.
Check if webmin is successfully sending emails with the test email features. I think it is on the send email category I’m webmin settings.