From: Alwin Antreich via pve-user <pve-user@lists.proxmox.com>
To: gaio@lilliput.linux.it
Cc: Alwin Antreich <alwin@antreich.com>,
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 [thread overview]
Message-ID: <mailman.312.1724078888.302.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <4hubpk-8fg1.ln1@leia.lilliput.linux.it>
[-- 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
next prev parent reply other threads:[~2024-08-19 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 13:39 Marco Gaiarin
2024-08-19 14:17 ` dORSY via pve-user
2024-08-19 14:47 ` Alwin Antreich via pve-user [this message]
[not found] ` <11e39814096a53c52422b9f2114719dd5ad73090@antreich.com>
2024-08-19 15:42 ` Marco Gaiarin
2024-08-19 19:10 ` dORSY via pve-user
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.312.1724078888.302.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=alwin@antreich.com \
--cc=gaio@lilliput.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox