Node can't ping another node after reboot no Corosync

CelticWebs

Member
Mar 14, 2023
75
3
8
I rebooted a node and now I'm unable to get sync with it, I get the error Cannot initialize CMAP service. I can;t get it to launch VMS due to lack of Quorum. I also can't do vvecm expect 1 as I get the same error about CMAP service.

I'm able to due apt update so I have network. I am unable to ping the other node and the other node is unable to ping this node.

cat /etc/pve/.members on the faulty node shows

Code:
{
"nodename": "pve847",
"version": 0
}
root@pve847:~# cat /etc/pve/.members
{
"nodename": "pve847",
"version": 0
}

The same command the node that is up and running says

Code:
{
"nodename": "prox380",
"version": 3,
"cluster": { "name": "CelticWebs", "version": 2, "nodes": 2, "quorate": 1 },
"nodelist": {
  "prox380": { "id": 1, "online": 1, "ip": "X.X.X.X"},
  "pve847": { "id": 2, "online": 0}
  }
}

I noticed firewall was enabled with no options, not sure how or why as its was a new install. Wasn't able to disable it in GUI due to the error telling me it can't lock a file and no quorum. I disabled this via command line but still no dice!

I've looked at the corosync file and they both look the same. I'm at a loss. What can I do to find out why they can't talk and get the server back online?
 
***Update***
turning off the firewall did actually allow the devices to ping each other. Still no sync though :(

currently I managed to stop corosync and work in local mode, just to get vms up.
 

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!