Cluster Setup Failed

TasMot

Active Member
Oct 29, 2018
13
0
41
64
Hi,
I am migrating VMs from ESXI and XenServer. So, I set up a ProxMox host (version 5.2-1) as ProxMox1 . I migrated 10 VMs to it. The prior XenServer was then converted to a new ProxMox server (version 5.3-11) as ProxMox2 and then I migrated 7 VMs to it. Now I am at the point that I converted a 2nd XenServer host to ProxMox as ProxMox3. No VMs are on it.
I Created a new Cluster on ProxMox2. Then I tried to join ProxMox3 using the GUI to the cluster on ProxMox2. This is where the problems began. Now ProxMox3 shows as part of the cluster but all of the storage shows a question mark decoration. The host shows an "x" in a red circle decoration.
upload_2019-3-2_13-10-18.png

The only thing "working" for ProxMox3 is the console:
upload_2019-3-2_13-11-23.png

Any other menu options just provide a spinning "loading" which eventually turns into a "communications failurre (0)" . I can SSH into the host via Putty and WinSCP.

Since ProxMox3 would not come up, neither would ProxMox2. I used "pvecm expected 1" on ProxMox2 in order to get the 2 VMs I wanted to come up.

On ProxMox2 I executed the command: systemctl status corosync.service and got:

upload_2019-3-2_13-21-47.png

Then "journalctl -xe" and got:
upload_2019-3-2_13-25-7.png

On ProxMox3 I executed the command: systemctl status corosync.service and got:
upload_2019-3-2_13-25-58.png


Then "journalctl -xe" on ProxMox3 and got:
upload_2019-3-2_13-16-58.png

When I started looking to see what else I could find, I used WinSCP to look at ProxMox3 (the failing node) in /etc/pve and found a bunch of broken links:
upload_2019-3-2_13-28-3.png

Before I really hose anything up, it looks like this might be the problem:

Mar 02 13:22:04 ProxMox2 pveproxy[10886]: unable to read '/etc/pve/nodes/ProxMox3/pve-ssl.pem' - No such file or directory

But, everything below /etc/pve is missing and I don't want to just start creating things and mess something up.

Any idea how this can be fixed?
 
You only work with IPv6? I would recommend you to use IPv4 only, but I don't now if it has to work with IPv6.
 
You only work with IPv6? I would recommend you to use IPv4 only, but I don't now if it has to work with IPv6.

Both boxes are configured to work with a dual stack. The NAS storage is IPv6 but a lot of the rest of the network is IPv4.

UPDATE: OK, I lied. The intention was that both boxes have IPv6 configured. For some reason the IPv6 was not working on the ProxMox3 box. NOW, I can ping all around and that part seems to be working. At least Corosync believes it can see both boxes. Next problem (which will be a new ticket), is that there seems to be a problem with certificates. "unable to read '/etc/pve/nodes/ProxMox3/pve-ssl.pem' - No such file or directory", but I need to do some more research first.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!