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 9FD7B1FF16D for ; Mon, 19 Aug 2024 17:45:15 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EB0711BF0C; Mon, 19 Aug 2024 17:45:31 +0200 (CEST) Date: Mon, 19 Aug 2024 17:42:58 +0200 From: Marco Gaiarin To: pve-user@lists.proxmox.com Message-ID: References: <4hubpk-8fg1.ln1@leia.lilliput.linux.it> <11e39814096a53c52422b9f2114719dd5ad73090@antreich.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <11e39814096a53c52422b9f2114719dd5ad73090@antreich.com> Organization: Casa Gaiarin User-Agent: Mutt/2.2.12 (2023-09-09) X-SPAM-LEVEL: Spam detection results: 0 AWL 0.395 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_PASS -0.1 DMARC pass policy JMQ_SPF_NEUTRAL 0.5 SPF set to ?all KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 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.001 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.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [PVE-User] Hardware watchdog for standalone server... X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE user list Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" Mandi! Alwin Antreich In chel di` si favelave... > Dow you want to make your VM/CT HA? That only works reliably with 3x nodes for > quorum (or 2x nodes & qdevice) [0]. I know. No. I'm speaking about standalone servers. > 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]. I'm saying EXACTLY that (also for dORSY): i need some sort of watchdog daemon, or the HA watchdog daemon 'watchdog-mux' works even in standalone setup? > Though I'd like to add that > resetting nodes continuously (issue is reoccurring), increases the chances for > data corruption. If there's some hardware or other trouble that trigger watchdog, typically the box is just TOFU and a reset cannot do more harm... at least this is my experience. -- _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user