@wlp94114 I had the same error. My ISO repository is on an SMB share, but the files were not readable by the ID I had mounted the share with in Xen. I corrected the permission on the file, and could get the VM to start.

@DustyArmstrong
Hi Dusty,

I set mine to concurrency = 1, then set the config backup to be 1/2 hour before the VM backup, and had no further issues.

Just a guess, but space the execution times out so the jobs have no overlap in execution times, and set concurrency = 1.

I use the rovinray docker image, with stock defaults except for allowing NFS mounts. I use Portainer to manage docker, and can send my template file (same as docker compose).

All the best,
Mark

@DustyArmstrong Hi Dusty,
Same error here, and I'm running XO in docker too.

I just updated the docker container image, and I found that I had two backups running to the same remote. I changed it to one script, and set the concurrency (under settings, advanced) to 2. I have not had that error since then.

Hope it helps.

Mark

@wlp94114 I had the same error. My ISO repository is on an SMB share, but the files were not readable by the ID I had mounted the share with in Xen. I corrected the permission on the file, and could get the VM to start.