[pve-devel] watchdog-mux.socket has been removed, but not disabled

[Thomas Lamprecht]

On 01/25/2016 07:59 AM, Michael Rasmussen wrote:
> On Mon, 25 Jan 2016 07:41:32 +0100
> Thomas Lamprecht <t.lamprecht at proxmox.com> wrote:
>
>> But doesn't executing the systemctl disable command not just removes the link from /etc/systemd/system/<targetname>/ ?
>>
> Yes, but other daemons could have dependencies or the internal event
> handler still contains references to the said daemon.
> A reboot as suggested by Thomas or running: systemctl daemon-reload
> should fix the problem. I tend to favor systemctl daemon-reload since
> reboot always should be a last resort.

We do a systemctl daemon-reload, dietmar cleaned up my commit regarding 
this:

https://git.proxmox.com/?p=pve-ha-manager.git;a=blobdiff;f=debian/postinst;h=e966057ca4f65fe6ba7ec5a94c0fccffd8a53087;hp=def84e0b91f8e3a864e10506e6423db471d80883;hb=b3395c8a8d95ea40d36e843e0a015dfc40faa6bb;hpb=8415603b298f43140a375e9b89253a8889f89221

Closing all connections to watchdog-mux, i.e. stopping the pve-ha-lrm 
and pve-ha-crm services and then restarting the watchdog-mux service 
(not socket) could also resolve this,
but I'm now guessing a bit, will test also :)