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 CC3B261B00 for <pve-devel@lists.proxmox.com>; Tue, 15 Sep 2020 10:42:46 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B750317BD3 for <pve-devel@lists.proxmox.com>; Tue, 15 Sep 2020 10:42:16 +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 3D3AC17BC9 for <pve-devel@lists.proxmox.com>; Tue, 15 Sep 2020 10:42:16 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id 057EC1A5C740; Tue, 15 Sep 2020 10:42:16 +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 gW6zsSoubD_2; Tue, 15 Sep 2020 10:42:15 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id DB2A61A5C741; Tue, 15 Sep 2020 10:42:15 +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 1UShSP6170Ka; Tue, 15 Sep 2020 10:42:15 +0200 (CEST) Received: from mailpro.odiso.net (mailpro.odiso.net [10.1.31.111]) by mailpro.odiso.net (Postfix) with ESMTP id C453E1A5C740; Tue, 15 Sep 2020 10:42:15 +0200 (CEST) Date: Tue, 15 Sep 2020 10:42:15 +0200 (CEST) From: Alexandre DERUMIER <aderumier@odiso.com> To: dietmar <dietmar@proxmox.com> Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com> Message-ID: <1746620611.752896.1600159335616.JavaMail.zimbra@odiso.com> In-Reply-To: <1227203309.12.1600154034412@webmail.proxmox.com> References: <216436814.339545.1599142316781.JavaMail.zimbra@odiso.com> <803983196.1499.1600067690947@webmail.proxmox.com> <2093781647.723563.1600072074707.JavaMail.zimbra@odiso.com> <88fe5075-870d-9197-7c84-71ae8a25e9dd@proxmox.com> <1775665592.735772.1600098305930.JavaMail.zimbra@odiso.com> <487514223.9.1600148741895@webmail.proxmox.com> <295606419.745430.1600151269212.JavaMail.zimbra@odiso.com> <1227203309.12.1600154034412@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: lmWFdNPil+vFbWG2X6xcUMRyNAyc7w== X-SPAM-LEVEL: Spam detection results: 0 AWL 0.035 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: Tue, 15 Sep 2020 08:42:46 -0000 >>pmxcfs cannot send anything in that case, so it is impossible that this h= as effects on other nodes. yes, I understand that, but I was thinking of the case if corosync is in st= opping phase (not totally stopped). Something racy (I really don't known). I just send 2 patch to start pve-cluster && corosync after syslog, like thi= s we'll have shutdown logs too. (I'm currently try to reproduce the problem, with reboot loops, but I still= can't reproduce it :/ ) ----- Mail original ----- De: "dietmar" <dietmar@proxmox.com> =C3=80: "aderumier" <aderumier@odiso.com> Cc: "Thomas Lamprecht" <t.lamprecht@proxmox.com>, "Proxmox VE development d= iscussion" <pve-devel@lists.proxmox.com> Envoy=C3=A9: Mardi 15 Septembre 2020 09:13:53 Objet: Re: [pve-devel] corosync bug: cluster break after 1 node clean shutd= own > I ask the question, because the 2 times I have problem, it was when shutt= ing down a server.=20 > So maybe some strange behaviour occur with both corosync && pmxcfs are st= opped at same time ?=20 pmxcfs cannot send anything in that case, so it is impossible that this has= effects on other nodes.=20