Search results

and the second time today i have to restart all corosyncs any idea?

Done and today did not unblock again:(

Sep 9 20:29:47 pve9 corosync[2408]: [MAIN ] Totem is unable to form a cluster because of an operating system or network fault (reason: totem is continuously in gather state). The most common cause of this message is that the local firewall is configured improperly. Again broken and did not...

do I have to reboot?

sorry, I forgot 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-5.0.15-1-pve: 5.0.15-1 ceph-fuse: 12.2.11+dfsg1-2.1 corosync: 3.0.2-pve2 criu: 3.11-3 glusterfs-client: 5.5-3...

Hi Guys, every Day my remote Connected Machine lets the Cluster go bad Sep 9 03:39:14 pve9 corosync[14541]: [MAIN ] Totem is unable to form a cluster because of an operating system or network fault (reason: totem is continuously in gather state). The most common cause of this message is...

following workflow if forgot to enable agent shutdown machine set qemu agent to enabled start vm add vioserial driver to pci simple commiunication cotroller install qemu guest-agent if not already done i would apreciate a package like the vmware tools thats automaticly detects and installs all...

Guten morgen. Nach dem Switch Tausch gab es übers Wochenende keine Probleme!!!

https://mail2.sysops.de/owncloud/s/D31lgoy2jriTdlU pve1 log is massive

i´d like to provide full log. its confusing and overloaded, if you like to where do i find it without journalctl?

bitteschön:) 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 pve-kernel-4.15.18-12-pve: 4.15.18-36...

my temporary switch is suspected. i replaced him today massive load 450 because of zfs replication pve2 was 40 without reason. after i resetted (old, but almost new) machines came back and load went back to normal

Jul 25 18:28:01 pve1 systemd[1]: Started Proxmox VE replication runner. Same time the corosync service failed Problems started when I set up a ZFS Replication Job. The Job did not work and i removed it later. It remained a while, but vanished then

at this moment i cant vnc from pve1 to pve2 then restart corosync on pve2 logged on to pve2 i can vnc any, but not on pve1

daily disconnect, restart at 22:37 did the job pve1 Jul 24 18:28:17 pve1 systemd[1]: Starting The Proxmox VE cluster filesystem... Jul 24 18:28:17 pve1 pmxcfs[5747]: [quorum] crit: quorum_initialize failed: 2 Jul 24 18:28:17 pve1 pmxcfs[5747]: [quorum] crit: can't initialize service Jul 24...

reboot was fine yesterday pve1 Jul 21 19:50:54 pve1 pmxcfs[8219]: [dcdb] notice: data verification successful Jul 21 20:50:54 pve1 pmxcfs[8219]: [dcdb] notice: data verification successful Jul 21 21:50:54 pve1 pmxcfs[8219]: [dcdb] notice: data verification successful Jul 21 22:50:54 pve1...

no ha. fresh installation last week with v5 and upgrade to 6 second directly installed v6 where is the cluster log located? i rebooted the second when i started that thread

Monitoring is fine. No Complaints pve1 Jul 22 09:45:14 pve1 corosync[52871]: [CPG ] downlist left_list: 0 received Jul 22 09:45:14 pve1 corosync[52871]: [CPG ] downlist left_list: 0 received Jul 22 09:53:44 pve1 corosync[52871]: [KNET ] link: host: 2 link: 0 is down Jul 22 09:53:45...

LAN Little load

just again restart corosync fixed https://pastebin.com/SiDsHyLy