From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <f.gruenbichler@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 0F50762251 for <pve-devel@lists.proxmox.com>; Tue, 29 Sep 2020 15:28:27 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 011261023E for <pve-devel@lists.proxmox.com>; Tue, 29 Sep 2020 15:28:27 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id DA69A10232 for <pve-devel@lists.proxmox.com>; Tue, 29 Sep 2020 15:28:25 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 99E7943F99 for <pve-devel@lists.proxmox.com>; Tue, 29 Sep 2020 15:28:25 +0200 (CEST) Date: Tue, 29 Sep 2020 15:28:19 +0200 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= <f.gruenbichler@proxmox.com> To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> References: <216436814.339545.1599142316781.JavaMail.zimbra@odiso.com> <1601282139.yqoafefp96.astroid@nora.none> <936571798.1335244.1601285700689.JavaMail.zimbra@odiso.com> <260722331.1517115.1601308760989.JavaMail.zimbra@odiso.com> <1601368526.gv9th0ekl0.astroid@nora.none> <1140250655.1944706.1601372261446.JavaMail.zimbra@odiso.com> <1740926248.1973796.1601376764334.JavaMail.zimbra@odiso.com> <596957573.1989195.1601379788390.JavaMail.zimbra@odiso.com> <528275552.1989337.1601380258730.JavaMail.zimbra@odiso.com> In-Reply-To: <528275552.1989337.1601380258730.JavaMail.zimbra@odiso.com> MIME-Version: 1.0 User-Agent: astroid/0.15.0 (https://github.com/astroidmail/astroid) Message-Id: <1601385859.kkbi3kzm1m.astroid@nora.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL -0.089 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium 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, 29 Sep 2020 13:28:27 -0000 huge thanks for all the work on this btw! I think I've found a likely culprit (a missing lock around a=20 non-thread-safe corosync library call) based on the last logs (which=20 were now finally complete!). rebuilt packages with a proof-of-concept-fix: 23b03a48d3aa9c14e86fe8cf9bbb7b00bd8fe9483084b9e0fd75fd67f29f10bec00e317e2a6= 6758713050f36c165d72f107ee3449f9efeb842d3a57c25f8bca7 pve-cluster_6.1-8_am= d64.deb 9e1addd676513b176f5afb67cc6d85630e7da9bbbf63562421b4fd2a3916b3b2af922df5550= 59b99f8b0b9e64171101a1c9973846e25f9144ded9d487450baef pve-cluster-dbgsym_6= .1-8_amd64.deb I removed some logging statements which are no longer needed, so output=20 is a bit less verbose again. if you are not able to trigger the issue=20 with this package, feel free to remove the -debug and let it run for a=20 little longer without the massive logs. if feedback from your end is positive, I'll whip up a proper patch=20 tomorrow or on Thursday. =