I am running proxmox version 6.4 and am looking to join a new node to my 3 node cluster. I went through the guide at https://pve.proxmox.com/wiki/Cluster_Manager#pvecm_join_node_to_cluster however it ended up in a bad state where the node being added is in a state of limbo.
The UI not loading on the new host,
The existing UI for the cluster showing unable to communicate to the new node in the UI "tls_process_server_certificate: certificate verify failed (596)"
The current cluster node (#4) giving this error in syslog "mon-proxmox-4 pveproxy[8126]: '/etc/pve/nodes/mon-proxmox-6/pve-ssl.pem' does not exist!#012"
I noticed that /etc/pve is missing some things (compared with a node in the cluster) and it's not writeable.
corosync.conf and authkey both have have the same md5sums on each host, respectively
corosync shows 3 members with quorum for the existing cluster and 1 member and no quorum for the new node.
All nodes have /etc/hosts set prior to adding the new node to the cluster with the ip / dns of all nodes.
I am sure I need to provide more details to figure out what is going on, is there any documentation that goes over what is happening on the backend to add a node, this way I can go through that sequentially and see what is failing?
Also of course hoping its something simple however, at this moment, I am at a loss and definitely don't want to make things worse for the existing cluster nodes.
Many Thanks
-Charles
The UI not loading on the new host,
The existing UI for the cluster showing unable to communicate to the new node in the UI "tls_process_server_certificate: certificate verify failed (596)"
The current cluster node (#4) giving this error in syslog "mon-proxmox-4 pveproxy[8126]: '/etc/pve/nodes/mon-proxmox-6/pve-ssl.pem' does not exist!#012"
I noticed that /etc/pve is missing some things (compared with a node in the cluster) and it's not writeable.
corosync.conf and authkey both have have the same md5sums on each host, respectively
corosync shows 3 members with quorum for the existing cluster and 1 member and no quorum for the new node.
All nodes have /etc/hosts set prior to adding the new node to the cluster with the ip / dns of all nodes.
I am sure I need to provide more details to figure out what is going on, is there any documentation that goes over what is happening on the backend to add a node, this way I can go through that sequentially and see what is failing?
Also of course hoping its something simple however, at this moment, I am at a loss and definitely don't want to make things worse for the existing cluster nodes.
Many Thanks
-Charles