watchdog-mux.service selected for restart on upgrades

[MaFL]

Hi,

why is the watchdog-mux.service selected for restart on apt upgrades?



For me this results in an instant reboot of the node in the ha-cluster.
It´s also discussed here: https://pve.proxmox.com/pipermail/pve-devel/2015-December/018511.html and it seems like this shouldn´t happen.

Any ideas?
Thanks!

 

[fabian]

we don't install needrestart by default, and needrestart requires tuning of the default include/exclude lists to work reliably. watchdog-mux does not link against anything that should require a restart (except for libc, in which case you probably are upgrading from one major release to the next and will reboot shortly anyway). the linked discussion is about something only tangentially related (that restarting watchdog-mux is problematic).

 

[MaFL]

Thanks for pointing me in the right direction. In the past I used apt-dater and a dependency of apt-dater-host is needrestart! Therefore it was installed.

 

[fabian]

needrestart is a nice tool (I use it on my systems I manage ) - but you need to tune the lists a bit to exclude stuff that triggers false-positives or should not be restarted.