Hello!
We have the problem that very often Veeam fails to start the worker.
Now the problem could be with Veeam or with Proxmox. I then always have to manually abort the worker start in Proxmox.
When I manually repeat the backup job, it usually works directly and the worker starts without problems.
In Proxmox itself I only see the following error message:
trying to acquire lock...TASK ERROR: can't lock file '/var/lock/qemu-server/lock-115.conf' - got timeout.
Which logs in Proxmox can I check to get a more detailed error message?
Greetings from Hamburg, Thorsten
We have the problem that very often Veeam fails to start the worker.
Now the problem could be with Veeam or with Proxmox. I then always have to manually abort the worker start in Proxmox.
When I manually repeat the backup job, it usually works directly and the worker starts without problems.
In Proxmox itself I only see the following error message:
trying to acquire lock...TASK ERROR: can't lock file '/var/lock/qemu-server/lock-115.conf' - got timeout.
Which logs in Proxmox can I check to get a more detailed error message?
Greetings from Hamburg, Thorsten