From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <aderumier@odiso.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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id F03F66139B for <pve-devel@pve.proxmox.com>; Sat, 5 Sep 2020 15:32:44 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DD1C32742B for <pve-devel@pve.proxmox.com>; Sat, 5 Sep 2020 15:32:43 +0200 (CEST) Received: from mailpro.odiso.net (mailpro.odiso.net [89.248.211.110]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 6500527413 for <pve-devel@pve.proxmox.com>; Sat, 5 Sep 2020 15:32:42 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id CE825185F426; Sat, 5 Sep 2020 15:32:41 +0200 (CEST) Received: from mailpro.odiso.net ([127.0.0.1]) by localhost (mailpro.odiso.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id LjJqgDlihBjQ; Sat, 5 Sep 2020 15:32:41 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id B40C7185F418; Sat, 5 Sep 2020 15:32:41 +0200 (CEST) X-Virus-Scanned: amavisd-new at mailpro.odiso.com Received: from mailpro.odiso.net ([127.0.0.1]) by localhost (mailpro.odiso.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id v_UAzmwuzlpm; Sat, 5 Sep 2020 15:32:41 +0200 (CEST) Received: from mailpro.odiso.net (mailpro.odiso.net [10.1.31.111]) by mailpro.odiso.net (Postfix) with ESMTP id 9BF14185F426; Sat, 5 Sep 2020 15:32:41 +0200 (CEST) Date: Sat, 5 Sep 2020 15:32:41 +0200 (CEST) From: Alexandre DERUMIER <aderumier@odiso.com> To: dietmar <dietmar@proxmox.com> Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, pve-devel <pve-devel@pve.proxmox.com> Message-ID: <1667839988.383835.1599312761359.JavaMail.zimbra@odiso.com> In-Reply-To: <481953113.753.1599234165778@webmail.proxmox.com> References: <216436814.339545.1599142316781.JavaMail.zimbra@odiso.com> <1044807310.366666.1599222580644.JavaMail.zimbra@odiso.com> <481953113.753.1599234165778@webmail.proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailer: Zimbra 8.8.12_GA_3866 (ZimbraWebClient - GC83 (Linux)/8.8.12_GA_3844) Thread-Topic: corosync bug: cluster break after 1 node clean shutdown Thread-Index: XHnO05OtFS+jxKW6SWx02/JzCF39qw== X-SPAM-LEVEL: Spam detection results: 0 AWL 0.033 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] corosync bug: cluster break after 1 node clean shutdown X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Sat, 05 Sep 2020 13:32:45 -0000 > Something like an extra heartbeat between nodes daemons, and check if we = also have quorum with theses heartbeats ?=20 > >>Was this even related to corosync? What exactly caused the reboot? Hi Dietmar, what I'm 100% sure, it that the watchdog have reboot all the servers. (I ha= ve watchdog trace in ipmi) That's happen, just after shutdown the server.=20 What is strange is that corosync logs on all servers show that they correct= ly the node down, and see other nodes. So, I really don't known. Maybe corosync what hanging ? I don't have any other logs from crm/lrm/pmxcs... I'm really blind. :/ ----- Mail original ----- De: "dietmar" <dietmar@proxmox.com> =C3=80: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>, = "aderumier" <aderumier@odiso.com> Cc: "pve-devel" <pve-devel@pve.proxmox.com> Envoy=C3=A9: Vendredi 4 Septembre 2020 17:42:45 Objet: Re: [pve-devel] corosync bug: cluster break after 1 node clean shutd= own > do you think it could be possible to add an extra optionnal layer of secu= rity check, not related to corosync ?=20 I would try to find the bug instead.=20 > I'm still afraid of this corosync bug since years, and still don't use HA= . (or I have tried to enable it 2months ago,and this give me a disaster yes= terday..)=20 >=20 > Something like an extra heartbeat between nodes daemons, and check if we = also have quorum with theses heartbeats ?=20 Was this even related to corosync? What exactly caused the reboot?=20