Search results

Another data point: I was able to log into the console and 'systemctl restart corosync'. and corosync seemed to come back up and regain quorum - but I still can't SSH into the box and that node in the GUI then changes from a grey question mark to a red X, just like as if it was powered down.

I've attached those files. It appears that corosync and/or pvesr are having issues. Thanks for your attention to this.

I have two clusters running the following version: root@vsys07:/var/log# pveversion -v proxmox-ve: 6.0-2 (running kernel: 5.0.21-1-pve) pve-manager: 6.0-6 (running version: 6.0-6/c71f879f) pve-kernel-5.0: 6.0-7 pve-kernel-helper: 6.0-7 pve-kernel-4.15: 5.4-6 pve-kernel-5.0.21-1-pve: 5.0.21-2...

I have ran it manually many times. There is no output because there are no errors. The pct snapshot command doesn't throw an error, it returns with no output, just like normal. The entry in the GUI tasks log shows up just like normal and the status is 'OK'. But (sometimes) the snapshot...

The underlying storage is local ZFS. zvols for VMs and zfs datasets for containers. root@vsys11:~# pct snapshot 120 periodic_running_2019_09_06_11_53_00 root@vsys11:~# This snapshot worked.

TL;DR It's not a syntax error in the script. Longer answer: The snapshot shows up in the GUI log. It's in the log as if it worked (no errors) and yet the snapshot doesn't actually happen. Sometimes it works, sometimes it doesn't, but it always shows up in the log as if it worked. It's the...

I have a script that snapshots all VMs and containers each night. After upgrading a few nights ago, 'pct snapshot' no longer works reliably. The script will issue the command, it shows up in the GUI log 'CT 119 - Snapshot', but the snapshot doesn't actually happen (sometimes - it's hit and...