Recent content by bolek2000

After looking at it nicely written down, I saw that I should also add --ns "$PBS_NAMESPACE"to my other commands, which now solved it. Thanks for watching ;-)

Hi, I have a Debian 11 turnkey linux fileserver running as LXC container under ProxmoxVE8. I backup the data with proxmox-backup-client to a remote PBS3 datastore, which seems to work without problems. Login to PBS and following works: proxmox-backup-client snapshot list --ns...

I was also experiencing this problem within PVE 4.4. I found out, that this can also happen if your VM has pending changes that need a shutdown/restart of the VM. In my case the VMs memory settings were changed and shown in red in the GUI. Even though there was enough space on the backup volume...

First I added 4 bridges without assigning IP addresses and rebooted. In this case the bridges didn't come up automatically, so I started them manually, but corosync was running I guess (not verified). Then I added an IP address to vmbr1 and rebooted, then the bridges came up automatically, but...

I installed corosync 2.3.5 under Ubuntu 16.04 32bit on old laptop and configured like in the howto. On all nodes i see Quorum information ------------------ Date: Sat Apr 1 23:41:16 2017 Quorum provider: corosync_votequorum Nodes: 3 Node ID: 3 Ring ID...

Ok, for Dell R610 the iDrac Watchdog was enabled (not sure if default), so I disabled it, as mentioned by ghusson above. Trying to set bmc-watchdog --set -a 3 -i 10 also failed with the same ipmi_watchdog driver error message. Then I enabled the iDrac Automated System Recovery Agent again and...

Update: I found something on the console: IPMI Watchdog: response: Error d4 on cmd 24 Google didn't really help, where to go with that one ? Kernel mailing list ? Dell tech center ? I don't have Pro support or alike.

Thanks for the good information, I configured the ipmi_watchdog on a Dell R610 and R720 according to your docs, but on one machine the timer is set coorectly after reboot and on the R610 not: #bmc-watchdog --get Timer Use: SMS/OS Timer: Running Logging...

I had the same problem recently and was looking in many directions...drivers etc., but it is only syntax: I also used the wrong comma syntax on one machine: slaves eth1, eth7 -> not working then I saw on the other machine, where it worked without comma: slaves eth1 eth7 -> working