Many services require restarting after upgrading to webmin 2.653

Webmin
1
SYSTEM INFORMATION
OS type and version Debian Linux 11.11
Webmin version 2.653
Theme version 26.50.4
Package updates All installed packages are up to date

After upgrading from webmin 2.652 to the recently release version 2.653 I have noticed a weird behavior by needrestart which runs automatically after apt upgrade; a bunch of services now require restarting:

# needrestart
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

Restarting services...
Service restarts being deferred:
 /etc/needrestart/restart.d/dbus.service
 systemctl restart fail2ban.service
 systemctl restart iscsid.service
 systemctl restart lxc-monitord.service
 systemctl restart pve-cluster.service
 systemctl restart pve-container@100.service
 systemctl restart pve-container@102.service
 systemctl restart pve-container@254.service
 systemctl restart pve-firewall.service
 systemctl restart pve-ha-crm.service
 systemctl restart pve-ha-lrm.service
 systemctl restart pve-lxc-syscalld.service
 systemctl restart pvedaemon.service
 systemctl restart pveproxy.service
 systemctl restart pvescheduler.service
 systemctl restart pvestatd.service
 systemctl restart rpcbind.service
 systemctl restart rrdcached.service
 systemctl restart rsyslog.service
 systemctl restart smartmontools.service
 systemctl restart spiceproxy.service
 systemctl restart ssh.service
 systemctl restart systemd-journald.service
 systemctl restart systemd-logind.service
 systemctl restart systemd-timesyncd.service
 systemctl restart systemd-udevd.service

This is pretty unusual for a webmin upgrade. What component that shared among these services does webmin have? ssh, fail2ban, rsyslog, systemd-journald, iscsid amongst others…

I’m almost sure the affected systems had no pending service restarts before this single package update.
I noticed the behavior on 2 systems, and put upgrading on hold for the rest of the systems for now.

Any idea? Have you noticed a similar behavior?

2

Nope, Those messages are generated by your OS, ask your OS provider as to why your OS needs to restart those services, but as a guess libc (or variant) has been updated

3

I have reviewed the apt logs thoroughly, reviewing each update done since the last system start up, and verifying that it wouldn’t trigger such a restart. No culprit was found.

Anyway, I needed to get some feedback from community. So, thank you. The forum shows 34 views of this post (so far).

Ask your OS provider

:slight_smile: I’m the system admin. It is my responsibility. I believe I’ve done the research. But I need to set up one more tool: An email notification when a reboot is needed, and luckily this has been discussed here recently, but needs to be tweaked to include LXCs and VMs.

4

so you know exactly what Debian has added as updates, do you work in the Debian infrastructure to know each commit they have made ?

5

Probably not a lot with Debian experience. :neutral_face:

6

No, I don’t.
And the same goes for webmin. Do I work in the webmin infrastructure to know each commit they have made? -No.
Hence why I’m posting here. I’m checking whether anyone else noticed a similar behavior to what I had.

Thank you for your feedback.

7

I can’t think of any reason for those to be related to a Webmin update.