Re: [PVE-User] Hardware watchdog for standalone server...

[Alwin Antreich via pve-user <pve-user@lists.proxmox.com>]

[-- Attachment #1: Type: message/rfc822, Size: 5093 bytes --]

From: "Alwin Antreich" <alwin@antreich.com>
To: gaio@lilliput.linux.it
Cc: "Proxmox VE user list" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Hardware watchdog for standalone server...
Date: Mon, 19 Aug 2024 14:47:30 +0000
Message-ID: <11e39814096a53c52422b9f2114719dd5ad73090@antreich.com>

Hallo Marco,



August 19, 2024 at 3:39 PM, "Marco Gaiarin" <gaio@lilliput.linux.it> wrote:



> 
> The use of a watchdog device (preferibly hardware, if not available,
> softdog) it is clear from:
> 
>  https://pve.proxmox.com/wiki/High_Availability
> 
> and in particular:
> 
>  https://pve.proxmox.com/wiki/High_Availability#ha_manager_fencing
> 
> where you can set (hardware) device module in /etc/default/pve-ha-manager .
> 
> But for a standalone server (or a cluster with no HA enabled) this still
> apply?! EG, /usr/sbin/watchdog-mux is a valid and general watchdog service,
> or better use insted some other services (like 'watchdog' daemon, or
> watchdog support bultin in systemd)?
> 
Dow you want to make your VM/CT HA? That only works reliably with 3x nodes for quorum (or 2x nodes & qdevice) [0].

But if you want to reset a node if it doesn't spin up a watchdog (doesn't respond), then you could use systemd watchdog[1]. Though I'd like to add that resetting nodes continuously (issue is reoccurring), increases the chances for data corruption.

Cheers,
Alwin

[0] https://pve.proxmox.com/wiki/High_Availability#_requirements
[1] https://0pointer.de/blog/projects/watchdog.html

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user