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 0DC2F8D0A3 for ; Mon, 7 Nov 2022 10:45:42 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D93F728839 for ; Mon, 7 Nov 2022 10:45:11 +0100 (CET) Received: from 14.mo582.mail-out.ovh.net (14.mo582.mail-out.ovh.net [46.105.56.113]) (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 ; Mon, 7 Nov 2022 10:45:10 +0100 (CET) Received: from player688.ha.ovh.net (unknown [10.109.156.76]) by mo582.mail-out.ovh.net (Postfix) with ESMTP id 03D3B25D3E for ; Mon, 7 Nov 2022 09:45:03 +0000 (UTC) Received: from riminilug.it (host-79-6-131-246.business.telecomitalia.it [79.6.131.246]) (Authenticated sender: piviul@riminilug.it) by player688.ha.ovh.net (Postfix) with ESMTPSA id 6BDAB305F5BD4; Mon, 7 Nov 2022 09:45:02 +0000 (UTC) Authentication-Results: garm.ovh; auth=pass (GARM-109S00327e94093-2bbe-4e02-98ea-1fd000c51abe, D2CAA6F38DC51FD01D751A62514153C2852E07C9) smtp.auth=piviul@riminilug.it X-OVh-ClientIp: 79.6.131.246 Message-ID: Date: Mon, 7 Nov 2022 10:45:01 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 Content-Language: it To: Eneko Lacunza , Proxmox VE user list References: <7523843a-2cdb-fd3a-1bb5-3423f47ee7ab@riminilug.it> <0ec3862e-69e4-4af3-b8ac-e1390d7ecd2b@binovo.es> From: Piviul In-Reply-To: <0ec3862e-69e4-4af3-b8ac-e1390d7ecd2b@binovo.es> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Ovh-Tracer-Id: 15248906865124608417 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvgedrvdekgddtjecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpefrihhvihhulhcuoehpihhvihhulhesrhhimhhinhhilhhughdrihhtqeenucggtffrrghtthgvrhhnpeegvdeutdfgffevvdfghedugeekgeelkefhteeigefggeeliefgffeileffkeegfeenucffohhmrghinhepphhrohigmhhogidrtghomhdpsghinhhovhhordgvshdphihouhhtuhgsvgdrtghomhdplhhinhhkvgguihhnrdgtohhmnecukfhppeduvdejrddtrddtrddupdejledriedrudefuddrvdegieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeduvdejrddtrddtrddupdhmrghilhhfrhhomhepoehpihhvihhulhesrhhimhhinhhilhhughdrihhtqedpnhgspghrtghpthhtohepuddprhgtphhtthhopehpvhgvqdhushgvrheslhhishhtshdrphhrohigmhhogidrtghomhdpoffvtefjohhsthepmhhoheekvddpmhhouggvpehsmhhtphhouhht X-SPAM-LEVEL: Spam detection results: 0 AWL -0.399 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_ASCII_DIVIDERS 0.8 Spam that uses ascii formatting tricks KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust RCVD_IN_MSPIKE_H3 -0.01 Good reputation (+3) RCVD_IN_MSPIKE_WL -0.01 Mailspike good senders 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-User] Quorum Activity blocked 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: Mon, 07 Nov 2022 09:45:42 -0000 Problem solved: I have restarted the switch and all now seems to work Piviul On 07/11/22 10:16, Eneko Lacunza wrote: > Hi Piviul, > > This is usually due to network connectivity issues. Are you able to > ping hosts on 192.168.255.* interfaces? > > El 7/11/22 a las 8:44, Piviul escribió: >> Good morning sirs, in a 3 nodes proxmox 6.4 all the 3 nodes seems to >> works, all vm guest continue to works but If I try to start a vm >> guest the starting fails with the message: "cluster not ready - no >> quorum? (500)". This is the cluster manager status: >> >> # pvecm status >> Cluster information >> ------------------- >> Name:             CSA-cluster1 >> Config Version:   3 >> Transport:        knet >> Secure auth:      on >> >> Quorum information >> ------------------ >> Date:             Mon Nov  7 08:37:20 2022 >> Quorum provider:  corosync_votequorum >> Nodes:            1 >> Node ID:          0x00000002 >> Ring ID:          2.91e >> Quorate:          No >> >> Votequorum information >> ---------------------- >> Expected votes:   3 >> Highest expected: 3 >> Total votes:      1 >> Quorum:           2 Activity blocked >> Flags: >> >> Membership information >> ---------------------- >>     Nodeid      Votes Name >> 0x00000002          1 192.168.255.2 (local) >> >> >> These are the first logs in syslog showing that some problem occurs: >> >> Nov  4 23:38:01 pve02 systemd[1]: Started Proxmox VE replication runner. >> Nov  4 23:38:26 pve02 corosync[1703]:   [KNET  ] link: host: 3 link: >> 0 is down >> Nov  4 23:38:26 pve02 corosync[1703]:   [KNET  ] host: host: 3 >> (passive) best link: 0 (pri: 1) >> Nov  4 23:38:26 pve02 corosync[1703]:   [KNET  ] host: host: 3 has no >> active links >> Nov  4 23:38:28 pve02 corosync[1703]:   [TOTEM ] Token has not been >> received in 2737 ms >> Nov  4 23:38:30 pve02 corosync[1703]:   [KNET  ] rx: host: 3 link: 0 >> is up >> Nov  4 23:38:30 pve02 corosync[1703]:   [KNET  ] host: host: 3 >> (passive) best link: 0 (pri: 1) >> Nov  4 23:38:32 pve02 corosync[1703]:   [QUORUM] Sync members[2]: 1 2 >> Nov  4 23:38:32 pve02 corosync[1703]:   [QUORUM] Sync left[1]: 3 >> Nov  4 23:38:32 pve02 corosync[1703]:   [TOTEM ] A new membership >> (1.873) was formed. Members left: 3 >> Nov  4 23:38:32 pve02 corosync[1703]:   [TOTEM ] Failed to receive >> the leave message. failed: 3 >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [dcdb] notice: members: 1/1626, >> 2/1578 >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [dcdb] notice: starting data >> syncronisation >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [status] notice: members: 1/1626, >> 2/1578 >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [status] notice: starting data >> syncronisation >> Nov  4 23:38:32 pve02 corosync[1703]:   [QUORUM] Members[2]: 1 2 >> Nov  4 23:38:32 pve02 corosync[1703]:   [MAIN  ] Completed service >> synchronization, ready to provide service. >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [dcdb] notice: received sync >> request (epoch 1/1626/00000009) >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [status] notice: received sync >> request (epoch 1/1626/00000009) >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [dcdb] notice: received all states >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [dcdb] notice: leader is 1/1626 >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [dcdb] notice: synced members: >> 1/1626, 2/1578 >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [dcdb] notice: all data is up to >> date >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [dcdb] notice: >> dfsm_deliver_queue: queue length 2 >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [status] notice: received all states >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [status] notice: all data is up >> to date >> Nov  4 23:38:32 pve02 pmxcfs[1578]: [status] notice: >> dfsm_deliver_queue: queue length 46 >> Nov  4 23:38:34 pve02 corosync[1703]:   [KNET  ] link: host: 3 link: >> 0 is down >> Nov  4 23:38:34 pve02 corosync[1703]:   [KNET  ] host: host: 3 >> (passive) best link: 0 (pri: 1) >> Nov  4 23:38:34 pve02 corosync[1703]:   [KNET  ] host: host: 3 has no >> active links >> Nov  4 23:38:41 pve02 corosync[1703]:   [KNET  ] link: host: 1 link: >> 0 is down >> Nov  4 23:38:41 pve02 corosync[1703]:   [KNET  ] host: host: 1 >> (passive) best link: 0 (pri: 1) >> Nov  4 23:38:41 pve02 corosync[1703]:   [KNET  ] host: host: 1 has no >> active links >> Nov  4 23:38:42 pve02 corosync[1703]:   [TOTEM ] Token has not been >> received in 2737 ms >> Nov  4 23:38:43 pve02 corosync[1703]:   [TOTEM ] A processor failed, >> forming new configuration: token timed out (3650ms), waiting 4380ms >> for consensus. >> Nov  4 23:38:48 pve02 corosync[1703]:   [QUORUM] Sync members[1]: 2 >> Nov  4 23:38:48 pve02 corosync[1703]:   [QUORUM] Sync left[1]: 1 >> Nov  4 23:38:48 pve02 corosync[1703]:   [TOTEM ] A new membership >> (2.877) was formed. Members left: 1 >> Nov  4 23:38:48 pve02 corosync[1703]:   [TOTEM ] Failed to receive >> the leave message. failed: 1 >> Nov  4 23:38:48 pve02 pmxcfs[1578]: [dcdb] notice: members: 2/1578 >> Nov  4 23:38:48 pve02 pmxcfs[1578]: [status] notice: members: 2/1578 >> Nov  4 23:38:48 pve02 corosync[1703]:   [QUORUM] This node is within >> the non-primary component and will NOT provide any services. >> Nov  4 23:38:48 pve02 corosync[1703]:   [QUORUM] Members[1]: 2 >> Nov  4 23:38:48 pve02 corosync[1703]:   [MAIN  ] Completed service >> synchronization, ready to provide service. >> Nov  4 23:38:48 pve02 pmxcfs[1578]: [status] notice: node lost quorum >> Nov  4 23:38:48 pve02 pmxcfs[1578]: [dcdb] crit: received write while >> not quorate - trigger resync >> Nov  4 23:38:48 pve02 pmxcfs[1578]: [dcdb] crit: leaving CPG group >> Nov  4 23:38:48 pve02 pve-ha-lrm[1943]: unable to write lrm status >> file - unable to open file '/etc/pve/nodes/pve02/lrm_status.tmp.1943' >> - Permission denied >> Nov  4 23:38:49 pve02 pmxcfs[1578]: [dcdb] notice: start cluster >> connection >> Nov  4 23:38:49 pve02 pmxcfs[1578]: [dcdb] crit: cpg_join failed: 14 >> Nov  4 23:38:49 pve02 pmxcfs[1578]: [dcdb] crit: can't initialize >> service >> Nov  4 23:38:55 pve02 pmxcfs[1578]: [dcdb] notice: members: 2/1578 >> Nov  4 23:38:55 pve02 pmxcfs[1578]: [dcdb] notice: all data is up to >> date >> Nov  4 23:39:00 pve02 systemd[1]: Starting Proxmox VE replication >> runner... >> Nov  4 23:39:01 pve02 pvesr[2146320]: trying to acquire cfs lock >> 'file-replication_cfg' ... >> [...] >> >> What's happened to my cluster? Someone has some suggestions to >> troubleshoot the problem? >> >> Piviul >> >> >> _______________________________________________ >> pve-user mailing list >> pve-user@lists.proxmox.com >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > Eneko Lacunza > Zuzendari teknikoa | Director técnico > Binovo IT Human Project > > Tel. +34 943 569 206 |https://www.binovo.es > Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun > > https://www.youtube.com/user/CANALBINOVO > https://www.linkedin.com/company/37269706/