From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-user-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id B5C8F1FF16D for <inbox@lore.proxmox.com>; Mon, 19 Aug 2024 16:47:54 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BD55E1AFAA; Mon, 19 Aug 2024 16:48:09 +0200 (CEST) Date: Mon, 19 Aug 2024 14:47:30 +0000 To: gaio@lilliput.linux.it In-Reply-To: <4hubpk-8fg1.ln1@leia.lilliput.linux.it> References: <4hubpk-8fg1.ln1@leia.lilliput.linux.it> MIME-Version: 1.0 Message-ID: <mailman.312.1724078888.302.pve-user@lists.proxmox.com> List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Post: <mailto:pve-user@lists.proxmox.com> From: Alwin Antreich via pve-user <pve-user@lists.proxmox.com> Precedence: list Cc: Alwin Antreich <alwin@antreich.com>, Proxmox VE user list <pve-user@lists.proxmox.com> X-Mailman-Version: 2.1.29 X-BeenThere: pve-user@lists.proxmox.com List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> Reply-To: Proxmox VE user list <pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> Subject: Re: [PVE-User] Hardware watchdog for standalone server... Content-Type: multipart/mixed; boundary="===============4080174695214321622==" Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" <pve-user-bounces@lists.proxmox.com> --===============4080174695214321622== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <alwin@antreich.com> X-Original-To: pve-user@lists.proxmox.com Delivered-To: pve-user@lists.proxmox.com Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 75141C5265 for <pve-user@lists.proxmox.com>; Mon, 19 Aug 2024 16:48:07 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 499651AF22 for <pve-user@lists.proxmox.com>; Mon, 19 Aug 2024 16:47:37 +0200 (CEST) Received: from mx.antreich.com (mx.antreich.com [173.249.42.230]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-user@lists.proxmox.com>; Mon, 19 Aug 2024 16:47:36 +0200 (CEST) Received: from mail2.antreich.com (unknown [172.16.9.25]) by mx.antreich.com (Postfix) with ESMTPS id D68296E2E1B; Mon, 19 Aug 2024 16:47:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antreich.com; s=2018; t=1724078851; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=WuMZ0uPX6qVCNJf0VQtzXTkPnU5qJUU33u/PqJt8EBE=; b=CI4ENiyUGT0kSK2Lc0lqWCI1oJVtZFvN/oh0lvdt9zF33Kt64Bg5zElLmJSQ6l9tulErUX p0EyKLtNqwC+l8UTvmFbNf8NQ/N3UeLN4mNFDgCtDoS4r7zFFxj/hRI69M8ILoYP6o3gVY EL/alm3HmkddmdDcY+Nrm83+48QfL6lG3LhtxEH6Oc2vTE5qJZZK0gnqYh7J5vqYALsEOm gTilUZY6SqZX+g/HpL7vKGt+QQgaTb3NqqcG62VGQXVtHeKumNUwV03NjkNVi+0N+IzpU5 yEzVDZ+wqJyaLWhlGGud8J2M0j6D7kfXLQIvVJjq12VtNy78qKa6GOQ5nFAR0A== MIME-Version: 1.0 Date: Mon, 19 Aug 2024 14:47:30 +0000 From: "Alwin Antreich" <alwin@antreich.com> Message-ID: <11e39814096a53c52422b9f2114719dd5ad73090@antreich.com> TLS-Required: No Subject: Re: [PVE-User] Hardware watchdog for standalone server... To: gaio@lilliput.linux.it Cc: "Proxmox VE user list" <pve-user@lists.proxmox.com> In-Reply-To: <4hubpk-8fg1.ln1@leia.lilliput.linux.it> References: <4hubpk-8fg1.ln1@leia.lilliput.linux.it> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.129 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy HTML_MESSAGE 0.001 HTML included in message 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 - Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Hallo Marco, August 19, 2024 at 3:39 PM, "Marco Gaiarin" <gaio@lilliput.linux.it> wrot= e: >=20 >=20The use of a watchdog device (preferibly hardware, if not available, > softdog) it is clear from: >=20 >=20 https://pve.proxmox.com/wiki/High_Availability >=20 >=20and in particular: >=20 >=20 https://pve.proxmox.com/wiki/High_Availability#ha_manager_fencing >=20 >=20where you can set (hardware) device module in /etc/default/pve-ha-man= ager . >=20 >=20But for a standalone server (or a cluster with no HA enabled) this st= ill > apply?! EG, /usr/sbin/watchdog-mux is a valid and general watchdog serv= ice, > or better use insted some other services (like 'watchdog' daemon, or > watchdog support bultin in systemd)? >=20 Dow=20you want to make your VM/CT HA? That only works reliably with 3x no= des 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]=C2=A0https://pve.proxmox.com/wiki/High_Availability#_requirements [1]=C2=A0https://0pointer.de/blog/projects/watchdog.html --===============4080174695214321622== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user --===============4080174695214321622==--