Node with 6.3 crashed entire cluster after join.

B

Bidi

Renowned Member
Feb 12, 2016
109
2
83
37
Hello

I have 5 servers in cluster all of them with proxmox 6.2 and i made a new server with 6.2 on it updated to 6.3 all whent just fine and i whanted to join the cluster with other servers.

After join the entire cluster is gone, i`m not even able to login to the new server only true ssh.

On other servers when i whant to join it just dosent show the Realm on the login page.

All servers ar online i`m able to login true ssh on all of them and sometimes like randomly even via web but not on the new node.

So i was thinking i have to update all the servers from 6.2-12 to 6.3 so i update them and still same problem.

I dont even know what to do nou, never had any issues like this in 5 years.
 
Now as i can see on one node

root@d3:~# systemctl status pve-cluster corososync
Unit corososync.service could not be found.
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2021-01-22 12:15:36 EET; 12min ago
Process: 2439 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)

Jan 22 12:15:36 d3 systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Jan 22 12:15:36 d3 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jan 22 12:15:36 d3 systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jan 22 12:15:36 d3 systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jan 22 12:15:36 d3 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jan 22 12:15:36 d3 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
root@d3:~# service pve-cluster restart
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
root@d3:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2021-01-22 12:28:26 EET; 7s ago
Process: 3428 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)

Jan 22 12:28:26 d3 systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Jan 22 12:28:26 d3 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jan 22 12:28:26 d3 systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jan 22 12:28:26 d3 systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jan 22 12:28:26 d3 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jan 22 12:28:26 d3 systemd[1]: Failed to start The Proxmox VE cluster filesystem.




root@d3:~# journalctl -xe
--
--
-- The unit pve-cluster.service has entered the 'failed' state with result 'exit-code'.
Jan 22 12:28:26 d3 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
-- Subject: A start job for unit pve-cluster.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-cluster.service has finished with a failure.
--
-- The job identifier is 19975 and the job result is failed.
Jan 22 12:28:26 d3 pve-ha-lrm[1284]: updating service status from manager failed: Connection refused
Jan 22 12:28:26 d3 pvestatd[1214]: ipcc_send_rec[1] failed: Connection refused
Jan 22 12:28:26 d3 pvestatd[1214]: ipcc_send_rec[2] failed: Connection refused
Jan 22 12:28:26 d3 pvestatd[1214]: ipcc_send_rec[3] failed: Connection refused
Jan 22 12:28:26 d3 pvestatd[1214]: ipcc_send_rec[4] failed: Connection refused
Jan 22 12:28:26 d3 pvestatd[1214]: status update error: Connection refused
Jan 22 12:28:28 d3 pve-firewall[1213]: status update error: Connection refused
Jan 22 12:28:28 d3 pveproxy[19638]: ipcc_send_rec[1] failed: Connection refused
Jan 22 12:28:28 d3 pveproxy[19638]: ipcc_send_rec[2] failed: Connection refused
Jan 22 12:28:28 d3 pveproxy[19638]: ipcc_send_rec[3] failed: Connection refused
Jan 22 12:28:29 d3 pveproxy[19638]: ipcc_send_rec[1] failed: Connection refused
Jan 22 12:28:29 d3 pveproxy[19638]: ipcc_send_rec[2] failed: Connection refused
Jan 22 12:28:29 d3 pveproxy[19638]: ipcc_send_rec[3] failed: Connection refused
Jan 22 12:28:29 d3 pveproxy[19638]: ipcc_send_rec[1] failed: Connection refused
Jan 22 12:28:29 d3 pveproxy[19638]: ipcc_send_rec[2] failed: Connection refused
Jan 22 12:28:29 d3 pveproxy[19638]: ipcc_send_rec[3] failed: Connection refused
 
You must log in or register to reply here.
Top Bottom