Search results

  1. 4 node cluster lost web GUI access

    Yes, it is very disappointing not to receive any feedback. I did solve the issue, and it was something completely unexpected. At one point, I used another device, and the web GUI loaded, indicating a problem on my main computer. After some more troubleshooting, I found that my network...
  2. 4 node cluster lost web GUI access

    Wow, I would have expected some feedback by now, am I missing something? My whole cluster and all of the VM's are down. I still can ssh into all nodes, but the web GUI will not load. Looks like I will have to reset all nodes, re-install PROXMOX and restore my VM's, not a lot of fun :-(
  3. 4 node cluster lost web GUI access

    root@pve-hn2:~# journalctl -b -u pve-cluster -- Journal begins at Fri 2021-10-15 07:17:26 AST, ends at Thu 2021-10-21 13:51:13 AST. -- Oct 21 06:44:55 pve-hn2 systemd[1]: Starting The Proxmox VE cluster filesystem... Oct 21 06:44:55 pve-hn2 pmxcfs[1028]: [quorum] crit: quorum_initialize failed...
  4. 4 node cluster lost web GUI access

    root@pve-hn2:~# wget --no-check-certificate https://localhost:8006 --2021-10-21 13:50:21-- https://localhost:8006/ Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:8006... connected. The certificate's owner does not match hostname ‘localhost’ HTTP...
  5. 4 node cluster lost web GUI access

    root@pve-hn2:~# pvecm nodes Membership information ---------------------- Nodeid Votes Name 2 1 pve-hn3 3 1 pve-hn2 (local) 4 1 pve-hn4
  6. 4 node cluster lost web GUI access

    root@pve-hn2:~# pvecm status Cluster information ------------------- Name: PVE-Cluster Config Version: 4 Transport: knet Secure auth: on Quorum information ------------------ Date: Thu Oct 21 13:48:03 2021 Quorum provider: corosync_votequorum Nodes...
  7. 4 node cluster lost web GUI access

    Last login: Thu Oct 21 06:32:41 2021 from 10.0.1.154 root@pve-hn2:~# pvecm status Cluster information ------------------- Name: PVE-Cluster Config Version: 4 Transport: knet Secure auth: on Quorum information ------------------ Date: Thu Oct 21 13:48:03...
  8. 4 node cluster lost web GUI access

    I have been running my cluster on the remaining 3 nodes until a few days ago, and now the web GUI does not load on any of them. I can ping all three and ssh into them. I did perform some new updates and rebooted but no web GUI loads? I did spend some time reading and performing a multitude of...
  9. 4 node cluster lost web GUI access

    root@pve-hn2:~# wget --no-check-certificate https://localhost:8006 --2021-10-08 15:00:58-- https://localhost:8006/ Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:8006... connected. The certificate's owner does not match hostname ‘localhost’ HTTP...
  10. 4 node cluster lost web GUI access

    root@pve-hn1:~# journalctl -b -u pve-cluster -- Journal begins at Thu 2021-10-07 20:27:40 AST, ends at Fri 2021-10-08 14:58:30 AST. -- Oct 08 13:16:48 pve-hn1 systemd[1]: Starting The Proxmox VE cluster filesystem... Oct 08 13:16:48 pve-hn1 pmxcfs[1148]: [quorum] crit: quorum_initialize failed...
  11. 4 node cluster lost web GUI access

    root@pve-hn1:~# corosync-cfgtool -s Could not initialize corosync configuration API error 2
  12. 4 node cluster lost web GUI access

    root@pve-hn1:~# pvecm status Cluster information ------------------- Name: PVE-Cluster Config Version: 4 Transport: knet Secure auth: on Cannot initialize CMAP service
  13. 4 node cluster lost web GUI access

    A couple of days ago, my 4 node cluster would not load the web GUI, for any node. I have ssh access to all 4 nodes and rebooted them many times. I read through the forum and followed some advice given to others with a similar issues, but things are just getting worse now. Node pve-hn4 is the...
  14. An error occured on the cluster node: corosync: link 1 exists in cluster config but wasn't specified for new node

    I rebooted each node and now they are showing up in the web GUI, and all looks to be working.
  15. An error occured on the cluster node: corosync: link 1 exists in cluster config but wasn't specified for new node

    Ok, not sure how this second link got in there, my cluster has been working fine for a long time. I manually edit the corosync.conf by removing the references to it on all nodes. I had to manually restart the corosync but after that, I was able to join the cluster. Except that the new node shows...
  16. An error occured on the cluster node: corosync: link 1 exists in cluster config but wasn't specified for new node

    And here is the version info: root@pve-hn2:~# pveversion -v proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve) pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e) pve-kernel-5.11: 7.0-7 pve-kernel-helper: 7.0-7 pve-kernel-5.4: 6.4-5 pve-kernel-5.3: 6.1-6 pve-kernel-5.11.22-4-pve: 5.11.22-8...
  17. An error occured on the cluster node: corosync: link 1 exists in cluster config but wasn't specified for new node

    logging { debug: off to_syslog: yes } nodelist { node { name: pve-hn1 nodeid: 1 quorum_votes: 1 ring0_addr: 10.0.1.243 ring1_addr: 10.0.1.243 } node { name: pve-hn2 nodeid: 3 quorum_votes: 1 ring0_addr: 10.0.1.244 ring1_addr: 10.0.1.244 }...
  18. An error occured on the cluster node: corosync: link 1 exists in cluster config but wasn't specified for new node

    HI, Looking for some help with adding 4th node to cluster. I have a 3 node cluster and I am trying to add another node. My 3 node cluster was running PVE6 and I successfully upgrade each node to PVE7 with no issues. The cluster remained intact and has full quorum. I prepared a new node with a...
  19. Unable to add a previous node to a cluster

    I should have mentioned this, but I already did try, pvecm add hn3 -f is this an even more aggressive option. I didn't see this command in any documentation? and all it does is keep waiting on quorum, just like run the above command: root@hn5:~# pvecm add hn3 --force can't create shared ssh...
  20. Unable to add a previous node to a cluster

    I removed a cluster node as per the documentation and re-installed PVE, when I try to add the node again to the cluster I keep getting this error. I ran this commandssh-keygen -R hn5 root@hn5:~# pvecm add hn3 can't create shared ssh key database '/etc/pve/priv/authorized_keys' authentication...

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 your own in 60 seconds.

Buy now!