Hi,
I've added a new node on my cluster, but there are some problems :
At boot, if I connect to this node, I see a question mark on all nodes, all VM - and no name appears for each VM, just "VM XXX" (where XXX is the VMID). But, I can see details about VM / node, it's working. After a few tens of seconds, interrogation marks disappear, replaced by usual green mark or VM icon with the good name.
I had some problems with name resolution at boot ; DNS is good, the same one that other nodes. I temporarily fix it with hosts file but I still have problems with these interrogation marks.
I see some errors at boot for pvescheduler :
But after service restart, all is OK :
No problems with cluster, I suppose, because all seems to be OK :
How can I fix it ?
Thanks.
I've added a new node on my cluster, but there are some problems :
At boot, if I connect to this node, I see a question mark on all nodes, all VM - and no name appears for each VM, just "VM XXX" (where XXX is the VMID). But, I can see details about VM / node, it's working. After a few tens of seconds, interrogation marks disappear, replaced by usual green mark or VM icon with the good name.
I had some problems with name resolution at boot ; DNS is good, the same one that other nodes. I temporarily fix it with hosts file but I still have problems with these interrogation marks.
I see some errors at boot for pvescheduler :
Code:
Dec 19 09:29:07 node-13 systemd[1]: Starting pvescheduler.service - Proxmox VE scheduler...
Dec 19 09:29:08 node-13 pvescheduler[5047]: starting server
Dec 19 09:29:08 node-13 systemd[1]: Started pvescheduler.service - Proxmox VE scheduler.
Dec 19 09:31:17 node-13 pvescheduler[5048]: replication: cfs-lock 'file-replication_cfg' error: got lock request timeout
Dec 19 09:31:17 node-13 pvescheduler[5049]: jobs: cfs-lock 'file-jobs_cfg' error: got lock request timeoutBut after service restart, all is OK :
Code:
Dec 19 09:54:17 node-13 systemd[1]: Starting pvescheduler.service - Proxmox VE scheduler...
Dec 19 09:54:18 node-13 pvescheduler[55932]: starting server
Dec 19 09:54:18 node-13 systemd[1]: Started pvescheduler.service - Proxmox VE scheduler.No problems with cluster, I suppose, because all seems to be OK :
Code:
Cluster information
-------------------
Name: CLOUD-XX
Config Version: 24
Transport: knet
Secure auth: on
Quorum information
------------------
Date: Tue Dec 19 09:41:10 2023
Quorum provider: corosync_votequorum
Nodes: 19
Node ID: 0x00000013
Ring ID: 1.13420
Quorate: Yes
Votequorum information
----------------------
Expected votes: 19
Highest expected: 19
Total votes: 19
Quorum: 10
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 XX.XX.XX.1
0x00000002 1 XX.XX.XX.2
0x00000003 1 XX.XX.XX.5
0x00000004 1 XX.XX.XX.4
0x00000005 1 XX.XX.XX.3
0x00000006 1 XX.XX.XX.80
0x00000007 1 XX.XX.XX.51
0x00000008 1 XX.XX.XX.52
0x00000009 1 XX.XX.XX.53
0x0000000a 1 XX.XX.XX.82
0x0000000b 1 XX.XX.XX.81
0x0000000c 1 XX.XX.XX.6
0x0000000d 1 XX.XX.XX.7
0x0000000e 1 XX.XX.XX.8
0x0000000f 1 XX.XX.XX.9
0x00000010 1 XX.XX.XX.10
0x00000011 1 XX.XX.XX.11
0x00000012 1 XX.XX.XX.12
0x00000013 1 XX.XX.XX.13 (local)How can I fix it ?
Thanks.
Last edited:
