Re: [PVE-User] Hardware watchdog for standalone server... - dORSY via pve-user

From: dORSY via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: dORSY <dorsyka@yahoo.com>
Subject: Re: [PVE-User] Hardware watchdog for standalone server...
Date: Mon, 19 Aug 2024 14:17:04 +0000 (UTC)	[thread overview]
Message-ID: <mailman.311.1724077650.302.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <4hubpk-8fg1.ln1@leia.lilliput.linux.it>

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

From: dORSY <dorsyka@yahoo.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Hardware watchdog for standalone server...
Date: Mon, 19 Aug 2024 14:17:04 +0000 (UTC)
Message-ID: <1084462757.5000300.1724077024331@mail.yahoo.com>

why wouldn't?if a hw watchdog times out (watchdogd does not reply in time) it would restart the server.that is a common thing, even standalone.

Yahoo Mail: Search, Organize, Conquer 

  On Mon, Aug 19, 2024 at 16:10, 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)?

Thanks.

-- 

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

[-- 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