Backup failed unable to connect to VM socket

RobFantini

Famous Member
May 24, 2012
2,015
102
133
Boston,Mass
One of 10 or so kvm's failed backup. A few before and after did a complete backup
Code:
105: Jul 28 04:25:37 INFO: Starting Backup of VM 105 (qemu)105: Jul 28 04:25:37 INFO: status = running
105: Jul 28 04:25:38 INFO: backup mode: snapshot
105: Jul 28 04:25:38 INFO: ionice priority: 7
105: Jul 28 04:25:38 INFO: suspend vm to make snapshot
105: Jul 28 04:25:38 INFO: VM 105 qmp command 'stop' failed - unable to connect to VM 105 socket - No such file or directory
105: Jul 28 04:25:38 INFO: unable to connect to VM 105 socket - No such file or directory
105: Jul 28 04:25:39 ERROR: Backup of VM 105 failed - command 'qm suspend 105 --skiplock' failed: exit code 255

I tried qm unlock 105 , and tried backuping up to local instead of nfs and got the same result.

Any suggestions?

I just realized : this node did get pve deb updates a couple of days ago , but can not be rebooted until later this weekend as it is in use. So after that reboot I'll try to backup VM 105.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!