Proxmox 9 Veeam 12.3.2 Worker start failed

Oct 4, 2025
2
4
3
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 same problem.

rm /var/lock/qemu-server/lock-<uid>.conf
qm unlock <uid>

solves the problem for the next start.

From my point of view the issue is that after the shutdown of the Veeam worker machine a lock in /var/lock/qemu-server still exists. I have a support case open with the Proxmox team as well as with Veeam - no luck so far.

Have you meanwhile a working solution/work around?

Best,
Frederik