From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 8E0A661667 for ; Sun, 6 Sep 2020 14:20:27 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 843502B554 for ; Sun, 6 Sep 2020 14:20: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 DB1A52B53C for ; Sun, 6 Sep 2020 14:20:26 +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 9E23B44A51 for ; Sun, 6 Sep 2020 14:20:26 +0200 (CEST) Date: Sun, 6 Sep 2020 14:19:43 +0200 (CEST) From: dietmar To: Alexandre DERUMIER , Proxmox VE development discussion Cc: pve-devel Message-ID: <1265645032.776.1599394783741@webmail.proxmox.com> In-Reply-To: <508219973.775.1599394447359@webmail.proxmox.com> References: <216436814.339545.1599142316781.JavaMail.zimbra@odiso.com> <1044807310.366666.1599222580644.JavaMail.zimbra@odiso.com> <481953113.753.1599234165778@webmail.proxmox.com> <1667839988.383835.1599312761359.JavaMail.zimbra@odiso.com> <665305060.757.1599319409105@webmail.proxmox.com> <1710924670.385348.1599327014568.JavaMail.zimbra@odiso.com> <469910091.758.1599366116137@webmail.proxmox.com> <570223166.391607.1599370570342.JavaMail.zimbra@odiso.com> <1059698258.392627.1599381816979.JavaMail.zimbra@odiso.com> <508219973.775.1599394447359@webmail.proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.3-Rev21 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL 0.095 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_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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Sep 2020 12:20:27 -0000 > On 09/06/2020 2:14 PM dietmar wrote: > > > > Sep 3 10:40:51 m6kvm7 pve-ha-lrm[16140]: loop take too long (87 seconds) > > Sep 3 10:40:51 m6kvm7 pve-ha-crm[16196]: loop take too long (92 seconds) > > Indeed, this should not happen. Do you use a spearate network for corosync? Or > was there high traffic on the network? What kind of maintenance was the reason > for the shutdown? Do you use the default corosync timeout values, or do you have a special setup?