From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id CF2DE1FF144 for ; Tue, 10 Mar 2026 16:53:02 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1D1E536AE; Tue, 10 Mar 2026 16:52:57 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH docs 1/2] ha-manager: document fencing & watchdog status Date: Tue, 10 Mar 2026 16:47:29 +0100 Message-ID: <20260310155216.2086316-2-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260310155216.2086316-1-t.lamprecht@proxmox.com> References: <20260310155216.2086316-1-t.lamprecht@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1773157909732 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.079 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.408 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.819 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.903 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: TSXDZQPONNGS4E5LNBN77HEFMC2BDD5Q X-Message-ID-Hash: TSXDZQPONNGS4E5LNBN77HEFMC2BDD5Q X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: This accompanies the recent changes in the ha-manager's status API endpoint to also include an explicit fencing/watchdog status. Signed-off-by: Thomas Lamprecht --- ha-manager.adoc | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/ha-manager.adoc b/ha-manager.adoc index 4c318fb..ee254be 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1003,6 +1003,34 @@ can lead to high load, especially on small clusters. Please design your cluster so that it can handle such worst case scenarios. +[[ha_manager_fencing_status]] +Fencing & Watchdog Status +~~~~~~~~~~~~~~~~~~~~~~~~~ + +The `ha-manager status` output includes a fencing entry that shows the CRM +watchdog state. Each LRM entry additionally shows its own watchdog state. + +armed:: + +The CRM is actively managing services and has its watchdog open. Each node's +LRM also holds a watchdog while it has its agent lock. On quorum loss or +daemon failure, the respective watchdog triggers a node reset to ensure safe +failover. + +standby:: + +The HA stack is ready but no CRM is actively running as master, for example +when no HA resources are configured yet or the cluster just started. The CRM +watchdog is not open. Fencing automatically transitions to `armed` once a CRM +takes over as master. + +NOTE: The `watchdog-mux` service keeps the underlying `/dev/watchdog` device +open for its entire lifetime, even when no HA client is connected. This +prevents other processes from claiming the device and ensures the HA stack can +always re-acquire it. Not all hardware watchdog drivers support magic close, so +closing the device could trigger an unintended reset. + + [[ha_manager_start_failure_policy]] Start Failure Policy --------------------- -- 2.47.3