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)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C16496266C for <pve-devel@lists.proxmox.com>; Wed, 16 Sep 2020 17:17:35 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A622825C54 for <pve-devel@lists.proxmox.com>; Wed, 16 Sep 2020 17:17:05 +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 C974525C49 for <pve-devel@lists.proxmox.com>; Wed, 16 Sep 2020 17:17:04 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id EEEB41A99226; Wed, 16 Sep 2020 17:17:02 +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 m4KVnaYMNV5c; Wed, 16 Sep 2020 17:17:02 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id D29831A99227; Wed, 16 Sep 2020 17:17:02 +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 Qp1lod_jk-bI; Wed, 16 Sep 2020 17:17:02 +0200 (CEST) Received: from mailpro.odiso.net (mailpro.odiso.net [10.1.31.111]) by mailpro.odiso.net (Postfix) with ESMTP id BABB11A99226; Wed, 16 Sep 2020 17:17:02 +0200 (CEST) Date: Wed, 16 Sep 2020 17:17:02 +0200 (CEST) From: Alexandre DERUMIER <aderumier@odiso.com> To: Thomas Lamprecht <t.lamprecht@proxmox.com> Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Message-ID: <65105078.871552.1600269422383.JavaMail.zimbra@odiso.com> In-Reply-To: <2bdde345-b966-d393-44d1-e5385821fbad@proxmox.com> References: <216436814.339545.1599142316781.JavaMail.zimbra@odiso.com> <597522514.840749.1600185513450.JavaMail.zimbra@odiso.com> <1097647242.851726.1600241667098.JavaMail.zimbra@odiso.com> <602718914.852368.1600243082185.JavaMail.zimbra@odiso.com> <1767271081.853403.1600245029802.JavaMail.zimbra@odiso.com> <1894376736.864562.1600253445817.JavaMail.zimbra@odiso.com> <2054513461.868164.1600262132255.JavaMail.zimbra@odiso.com> <2bdde345-b966-d393-44d1-e5385821fbad@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: kOsRfBKFsysuTCvARaK4OJYkjUVcZw== X-SPAM-LEVEL: Spam detection results: 0 AWL 0.079 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [odiso.net] 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: Wed, 16 Sep 2020 15:17:35 -0000 I have produce it again, with the coredump this time restart corosync : 17:05:27 http://odisoweb1.odiso.net/pmxcfs-corosync2.log bt full https://gist.github.com/aderumier/466dcc4aedb795aaf0f308de0d1c652b coredump http://odisoweb1.odiso.net/core.7761.gz ----- Mail original ----- De: "Thomas Lamprecht" <t.lamprecht@proxmox.com> =C3=80: "aderumier" <aderumier@odiso.com>, "Proxmox VE development discussi= on" <pve-devel@lists.proxmox.com> Envoy=C3=A9: Mercredi 16 Septembre 2020 16:45:12 Objet: Re: [pve-devel] corosync bug: cluster break after 1 node clean shutd= own On 9/16/20 3:15 PM, Alexandre DERUMIER wrote:=20 > I have reproduce it again, with pmxcfs in debug mode=20 >=20 > corosync restart at 15:02:10, and it was already block on other nodes at = 15:02:12=20 >=20 > The pmxcfs was still logging after the lock.=20 >=20 >=20 > here the log on node1 where corosync has been restarted=20 >=20 > http://odisoweb1.odiso.net/pmxcfs-corosync.log=20 >=20 thanks for those, I need a bit to sift through them. Seem like either dfsm = gets=20 out of sync or we do not get a ACK reply from cpg_send.=20 A full core dump would be still nice, in gdb:=20 generate-core-file=20 PS: instead of manually switching to threads you can do:=20 thread apply all bt full=20 to get a backtrace for all threads in one command=20