We are experiencing an issue with backup failures for a Proxmox Virtual Environment VM (VM ID: 105). The backups are being triggered via Veeam, but the failure appears to originate from the Proxmox layer.
Below are the relevant log excerpts observed during the failure:
ERROR: Backup of VM 105 failed – interrupted by signal
unable to connect to VM 105 QMP socket – timeout after 51 retries
TASK ERROR: can't lock file '/var/lock/qemu-server/lock-105.conf' – got timeout
Based on initial analysis and feedback from Veeam support, Proxmox is unable to connect to the QMP socket for the VM and is also unable to obtain a lock on the VM configuration file.
Actions already performed:
Verified VM status and running processes
Attempted VM restart and retried backup
Can you please assist with further troubleshooting.
Below are the relevant log excerpts observed during the failure:
ERROR: Backup of VM 105 failed – interrupted by signal
unable to connect to VM 105 QMP socket – timeout after 51 retries
TASK ERROR: can't lock file '/var/lock/qemu-server/lock-105.conf' – got timeout
Based on initial analysis and feedback from Veeam support, Proxmox is unable to connect to the QMP socket for the VM and is also unable to obtain a lock on the VM configuration file.
Actions already performed:
Verified VM status and running processes
Attempted VM restart and retried backup
Can you please assist with further troubleshooting.