guest-fsfreeze-freeze' failed // 'guest-fsfreeze-thaw' failed

[Manny Vazquez]

Checking into why my backups (for some VMs) I saw this errors

---------------------------
INFO: Starting Backup of VM 6001 (qemu)
INFO: status = running
INFO: update VM 6001: -lock backup
INFO: VM Name: w2012DocuphaseSql
INFO: include disk 'virtio0' 'local-zfs:vm-6001-disk-2' 100G
INFO: include disk 'virtio1' 'local-zfs:vm-6001-disk-3' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/usb5/dump/vzdump-qemu-6001-2019_04_23-04_59_46.vma'
ERROR: VM 6001 qmp command 'guest-fsfreeze-freeze' failed - unable to connect to VM 6001 qga socket - timeout after 35836 retries
ERROR: VM 6001 qmp command 'guest-fsfreeze-thaw' failed - unable to connect to VM 6001 qga socket - timeout after 101 retries
INFO: started backup task '1c475df9-b2f5-4362-aef0-b9ded0acc4f5'
---------------------------

It takes sometimes 2 hours to do the backup just because it sits there waiting for over 1 hour. Even that the 2 drives are 100G, one is used to like 20% the other about 1%, it is not the size of the drives.

I read in another post about the agent been installed, I do have the agent installed on the VMs and selected as 'yes' on the GUI.

Any solution to this?

 

[wolfgang]

Hi,

is the agent running?
Did you shut down the VM after you add the Guest option?

 

[Manny Vazquez]

Hi,

is the agent running?
Did you shut down the VM after you add the Guest option?

Yes and yes, several times.
These are other errors from today's backups. (Backups still run, and they are good, I tested several )
One completely failed.
----------------------------------------
INFO: Starting Backup of VM 3380 (qemu)
INFO: status = running
INFO: update VM 3380: -lock backup
INFO: VM Name: 3380-w2k8
INFO: include disk 'ide0' 'local-zfs:vm-3380-disk-1' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/usb5/dump/vzdump-qemu-3380-2019_04_24-00_19_37.vma'
closing with write buffer at /usr/share/perl5/IO/Multiplex.pm line 928.
ERROR: got timeout
INFO: aborting backup job
ERROR: Backup of VM 3380 failed - got timeout
INFO: Starting Backup of VM 3397 (qemu)
INFO: status = running
INFO: update VM 3397: -lock backup
INFO: VM Name: 3397-w2k8
INFO: include disk 'ide0' 'local-zfs:vm-3397-disk-1' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/usb5/dump/vzdump-qemu-3397-2019_04_24-00_19_47.vma'
ERROR: VM 3397 qmp command 'guest-fsfreeze-thaw' failed - got timeout
INFO: started backup task 'c031f240-d8fc-4ca6-888d-74bf54bb4f0f'
----------------------------------------------------------

And this again for the same error as listed in the original post
-----------------------------------------------------
INFO: Starting Backup of VM 6001 (qemu)
INFO: status = running
INFO: update VM 6001: -lock backup
INFO: VM Name: w2012DocuphaseSql
INFO: include disk 'virtio0' 'local-zfs:vm-6001-disk-2' 100G
INFO: include disk 'virtio1' 'local-zfs:vm-6001-disk-3' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/usb5/dump/vzdump-qemu-6001-2019_04_24-04_43_15.vma'
ERROR: VM 6001 qmp command 'guest-fsfreeze-freeze' failed - unable to connect to VM 6001 qga socket - timeout after 35827 retries
ERROR: VM 6001 qmp command 'guest-fsfreeze-thaw' failed - unable to connect to VM 6001 qga socket - timeout after 101 retries
INFO: started backup task '9919fd77-a11a-4dc8-9098-5b26d2849357'
----------------------------------------------------------------

This last one is the worst offender, it stays TRYING for 35thousand times (about one hour) .. I am killing this VM today or tomorrow..

But yes, I do follow the same procedure on all the VMs with the agent even that in some case it "works' and other dont, like in memory reporting for instance, in some cases it reports as using all the ram given to the vm, even when you go into the vm, and the usage is very low.