Search results

..and can you remove the solved tag? This Problem is not solved as long as many people are facing this issue...

Yes they where the -2 packages. but there was a ram problem in node2. this is fixed now. the problem with loosing quorum is still present

With the second set of packages the nodes are unstable. This is the third time one of the nodes isn't pingable anymore ans the only way to get it back is a hardreset

This time node 1 totally disapeared. I needed a hardreboot. only logs from node2 can be provided

The Nodes still loose quorum. I needed to delete some lines of the logs, because they where to big to upload. I'll now restart both nodes, install the other packages and restart them again. I'll report later if that changes anything

I've installed the http://download.proxmox.com/temp/libknet1_1.10-pve2~test1_amd64.deb now with untouched corosync.conf and will report...

I cant edit the corosync in the pve folder because of missing rights. i edited the one in /etc/corosync/corosync. Was that wrong? I missed to increase the version number. that's a good point

It didn't help. But: the corosync.conf is changed back after restart... i don't know why the token config disappears

The Cluster is healthy now for about 6 hours with token: 3000 added to the totem part of config. I will report tomorrow if it still works, but I think also with default und slow/unstable network the cluster should recover as soon as the network is stable enough again

I'll try this. But as i already mentioned: in my opinion the cluster should be back after network conditions are good enough again. For me it's a bug as long as i need to manually restart a service to work again

Also if the network may be to slow/unstable... the node should come back automatically after the network is stable enough. output for node 1: corosync-cmapctl -m stats stats.ipcs.global.active (u64) = 5 stats.ipcs.global.closed (u64) = 0 stats.ipcs.service0.1407.0x557be49144c0.dispatched (u64)...

and the other node. It's easy to identify where the magic happens...

addition to the posted config above here are the logs from one node

I provided all i know how to get it. please give exact instructions how to get the needed information. I don't understand why there are these Problems with Proxmox Clusters... I just want to configure and move vms vie webinterface.... that's the only part where i really miss vmware

root@p2:~# pveversion -v proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve) pve-manager: 6.0-4 (running version: 6.0-4/2a719255) pve-kernel-5.0: 6.0-5 pve-kernel-helper: 6.0-5 pve-kernel-4.15: 5.4-6 pve-kernel-5.0.15-1-pve: 5.0.15-1 pve-kernel-4.15.18-18-pve: 4.15.18-44 ceph-fuse...

corosync-cfgtool -s Printing link status. Local node ID 2 LINK ID 0 addr = 94.XXX.16.XXX status: nodeid 1: link enabled:1 link connected:1 nodeid 2: link enabled:1 link connected:1 root@p2:/var/log# pvecm status Quorum...

I've got the same problem. Same Setup: One Clusternode was upgraded from 5.4 to 6, the other node is new. They are NOT in the same network, but since knet this shouldn't be a problem. here is the output from proxmox node 2 journalctl -u pve-cluster Jul 26 08:37:41 p2 systemd[1]: Starting The...