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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 8560A944C2 for ; Wed, 11 Jan 2023 13:40:46 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 66B421DF32 for ; Wed, 11 Jan 2023 13:40:16 +0100 (CET) Received: from picard.linux.it (picard.linux.it [IPv6:2001:1418:10:5::2]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 11 Jan 2023 13:40:11 +0100 (CET) Received: by picard.linux.it (Postfix, from userid 10) id 2C1063CB57B; Wed, 11 Jan 2023 13:40:05 +0100 (CET) Received: from news by eraldo.lilliput.linux.it with local (Exim 4.89) (envelope-from ) id 1pFaKn-0001ra-6G for pve-user@lists.proxmox.com; Wed, 11 Jan 2023 13:36:01 +0100 From: Marco Gaiarin Date: Wed, 11 Jan 2023 09:16:40 +0100 Organization: Il gaio usa sempre TIN per le liste, fallo anche tu!!! Message-ID: <6s729j-uk8.ln1@hermione.lilliput.linux.it> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit X-Trace: eraldo.lilliput.linux.it 1673440144 6976 192.168.24.2 (11 Jan 2023 12:29:04 GMT) X-Mailer: tin/2.6.2-20220130 ("Convalmore") (Linux/5.15.0-57-generic (x86_64)) X-Gateway-System: SmartGate 1.4.5 To: pve-user@lists.proxmox.com X-SPAM-LEVEL: Spam detection results: 0 AWL -0.530 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DATE_IN_PAST_03_06 1.592 Date: is 3 to 6 hours before Received: date JMQ_SPF_NEUTRAL 0.5 SPF set to ?all KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [PVE-User] Relax corosync timeout... X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2023 12:40:46 -0000 In a 3 node PVE cluster i was forced, for now, to use a shared network for data and sync. When there's a traffic peak, i got: Jan 10 23:35:09 svpve3 corosync[2884]: [KNET ] link: host: 1 link: 0 is down Jan 10 23:35:09 svpve3 corosync[2884]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1) Jan 10 23:35:09 svpve3 corosync[2884]: [KNET ] host: host: 1 has no active links Jan 10 23:35:11 svpve3 corosync[2884]: [KNET ] rx: host: 1 link: 0 is up Jan 10 23:35:11 svpve3 corosync[2884]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1) Jan 10 23:35:19 svpve3 corosync[2884]: [KNET ] link: host: 1 link: 0 is down Jan 10 23:35:19 svpve3 corosync[2884]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1) Jan 10 23:35:19 svpve3 corosync[2884]: [KNET ] host: host: 1 has no active links Jan 10 23:35:21 svpve3 corosync[2884]: [KNET ] rx: host: 1 link: 0 is up Jan 10 23:35:21 svpve3 corosync[2884]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1) Jan 10 23:35:45 svpve3 corosync[2884]: [TOTEM ] Token has not been received in 2737 ms Jan 10 23:35:46 svpve3 corosync[2884]: [TOTEM ] A processor failed, forming new configuration: token timed out (3650ms), waiting 4380ms for consensus. Jan 10 23:35:48 svpve3 corosync[2884]: [QUORUM] Sync members[3]: 1 2 3 Jan 10 23:35:48 svpve3 corosync[2884]: [TOTEM ] A new membership (1.2fd) was formed. Members I've looked at 'man corosync.conf' but is not clear to me if and what parameter i can modify to have corosync prevent emit this warning too much. Thanks. -- Errare è umano, ma per fare veramente casino ci vuole la password di root (Zio Budda)