From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 6FC3F1FF133 for ; Mon, 27 Apr 2026 19:06:25 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8452C2459D; Mon, 27 Apr 2026 19:05:59 +0200 (CEST) From: =?UTF-8?q?Michael=20K=C3=B6ppl?= To: pve-devel@lists.proxmox.com Subject: [PATCH cluster v3 5/8] pvecm: warn users of high token timeouts when using status command Date: Mon, 27 Apr 2026 19:05:45 +0200 Message-ID: <20260427170548.307698-6-m.koeppl@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260427170548.307698-1-m.koeppl@proxmox.com> References: <20260427170548.307698-1-m.koeppl@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1777309455437 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.096 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 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: VFKHGNP2HLAHZISHI64MDXWB6BYL7CO5 X-Message-ID-Hash: VFKHGNP2HLAHZISHI64MDXWB6BYL7CO5 X-MailFrom: m.koeppl@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: If the calculated token timeout is above certain thresholds, display a warning for users when running `pvecm status` as part of the Cluster Information block. Also points users to the documentation regarding potential adaptations to their cluster configuration to alleviate the problem. Signed-off-by: Michael Köppl --- src/PVE/CLI/pvecm.pm | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/PVE/CLI/pvecm.pm b/src/PVE/CLI/pvecm.pm index 7d393a8..64e1d94 100755 --- a/src/PVE/CLI/pvecm.pm +++ b/src/PVE/CLI/pvecm.pm @@ -561,6 +561,18 @@ __PACKAGE__->register_method({ $print_info->('Transport', 'transport', 'knet'); $print_info->('Secure auth', 'secauth', 'off'); printf "\n"; + + my $nodelist = PVE::Corosync::nodelist($conf); + my $total_timeout_secs = PVE::Corosync::calculate_membership_recovery_timeout( + $totem, + scalar(keys %$nodelist), + ); + if ( + my $msg = + PVE::Corosync::get_membership_recovery_timeout_warning($total_timeout_secs) + ) { + warn "$msg\n\n"; + } } exec('corosync-quorumtool', '-siH'); -- 2.47.3