Recent content by Tommi2Day

OK, checked, all directories and files are owned by user backup. Then i rebooted all nodes and pbs again and restarted the jobs. Now it went trough. Dont know why. Maybe because the backup datastore is NFS

After I did my weekly update on pve and pbs, followed by reboot, unfortunately since then all backups are failing with backup connect failed: command error: Permission denied (os error 13) How to handle this? PBS 4.2.0 PVE 9.1.11 pve-manager/9.1.11/8eac2c86f015bdda linux 7.0.2-3-pve...

Yep, deleteing the cache and cookies was the solution. Thanks!

i recently updated my PVE 8 to the latest. Because there was a new kernel in i also rebooted the nodes afterwards. Now i am unable to access neither the node console nor the vm console with the gui console command. All other functions are working as usual (so far i checked). Do i have to...

Good advice, only the host pve3 was recorded there. I added the other hosts then console starts working. I am wondering this is really needed, as i have a good working dns for name resolution. And i rebooted the nodes already in the past without any problem. Thanks for pointing out & Best...

I had to reboot my PVE cluster on all nodes after serveral weeks flawless operation. After this i can't do pve update or access VM from gui. It terminates in any cases on any node similar this All nodes and vms are up and running properly, there is only this console issue > pveversion...

just did a quick test with testing packages and shutdown / restart successfully one Node without any issue. Also a backup works now again.

also PBS is complaining when backing up stopped VMs or templates for this reason 9001 ci-ubuntu-image FAILED 00:00:01 command '/sbin/bridge fdb append XX dev tap9001i0 master static' failed: exit code 255 9002 focal-base-202201 FAILED 00:00:01 command '/sbin/bridge fdb append XX dev...

yep, all of my servers (all with openvswitch) got this issue after upgrade and reboot

for terraform operations it was helpfull for me to limit parallelism to prevent this error.

for me was the same. Backup data store added flawless, but pvesm status fails with the verify error. I am using a custom certificate from private pki and alredy added the ca cert to the proxy.pem. Even PVE and PBS are using the same CA the PBS cert was not accepted. My solution was adding the...