[SOLVED] 'guest-fsfreeze-freeze' failed - got timeout

Discussion in 'Proxmox VE: Installation and configuration' started by killmasta93, Nov 10, 2017.

  1. killmasta93

    killmasta93 Member

    Joined:
    Aug 13, 2017
    Messages:
    404
    Likes Received:
    12
    Hi,
    I was wondering if someone else has had this issue before when backing up the VM?
    I was looking the web and did not really see much users get this is error. it does the backup fine but takes 1 hour because it gets stuck on the fsfreeze

    this is the log

    Code:
    )
    Task viewer: Backup
    Output
    Status
    Stop
    INFO: starting new backup job: vzdump 100 --storage local-USB --compress lzo --mode snapshot --node promethues --remove 0
    INFO: Starting Backup of VM 100 (qemu)
    INFO: status = running
    INFO: update VM 100: -lock backup
    INFO: VM Name: Olympus
    INFO: include disk 'virtio0' 'local-zfs:vm-100-disk-1' 127G
    INFO: backup mode: snapshot
    INFO: ionice priority: 7
    INFO: creating archive '/media/external/dump/vzdump-qemu-100-2017_11_05-22_29_03.vma.lzo'
    ERROR: VM 100 qmp command 'guest-fsfreeze-freeze' failed - got timeout
    ERROR: VM 100 qmp command 'guest-fsfreeze-thaw' failed - got timeout
    INFO: started backup task '26a14a4a-3898-435b-8a6f-c38c8d2a7225'
    INFO: status: 3% (4595515392/136365211648), sparse 3% (4582051840), duration 3, read/write 1531/4 MB/s
    INFO: status: 6% (8288993280/136365211648), sparse 6% (8274915328), duration 6, read/write 1231/0 MB/s
    INFO: status: 8% (11964973056/136365211648), sparse 8% (11950272512), duration 9, read/write 1225/0 MB/s
    INFO: status: 11% (15580135424/136365211648), sparse 11% (15564922880), duration 12, read/write 1205/0 MB/s
    INFO: status: 14% (19133890560/136365211648), sparse 14% (19117883392), duration 15, read/write 1184/0 MB/s
    INFO: status: 16% (22881828864/136365211648), sparse 16% (22865309696), duration 18, read/write 1249/0 MB/s
    INFO: status: 19% (26600275968/136365211648), sparse 19% (26583142400), duration 21, read/write 1239/0 MB/s
    INFO: status: 22% (30366498816/136365211648), sparse 22% (30348750848), duration 24, read/write 1255/0 MB/s
    INFO: status: 24% (33544601600/136365211648), sparse 24% (33520201728), duration 27, read/write 1059/2 MB/s
    INFO: status: 26% (36438081536/136365211648), sparse 26% (36392280064), duration 30, read/write 964/7 MB/s
    INFO: status: 29% (40017723392/136365211648), sparse 29% (39971373056), duration 33, read/write 1193/0 MB/s
    INFO: status: 32% (43745738752/136365211648), sparse 32% (43698774016), duration 36, read/write 1242/0 MB/s
    INFO: status: 34% (47396290560/136365211648), sparse 34% (47348711424), duration 39, read/write 1216/0 MB/s
    INFO: status: 37% (50977177600/136365211648), sparse 37% (50929078272), duration 42, read/write 1193/0 MB/s
    INFO: status: 40% (54611279872/136365211648), sparse 40% (54562566144), duration 45, read/write 1211/0 MB/s
    INFO: status: 42% (58319044608/136365211648), sparse 42% (58269818880), duration 48, read/write 1235/0 MB/s
    INFO: status: 45% (61994762240/136365211648), sparse 45% (61944922112), duration 51, read/write 1225/0 MB/s
    INFO: status: 47% (65280278528/136365211648), sparse 47% (65222262784), duration 54, read/write 1095/2 MB/s
    INFO: status: 50% (68343562240/136365211648), sparse 50% (68263530496), duration 57, read/write 1021/7 MB/s
    INFO: status: 51% (70107004928/136365211648), sparse 50% (69531856896), duration 68, read/write 160/45 MB/s
    INFO: status: 53% (73606889472/136365211648), sparse 53% (73029902336), duration 71, read/write 1166/0 MB/s
    INFO: status: 56% (77248790528/136365211648), sparse 56% (76671291392), duration 74, read/write 1213/0 MB/s
    INFO: status: 59% (80776462336/136365211648), sparse 58% (80197197824), duration 77, read/write 1175/0 MB/s
    INFO: status: 61% (84435992576/136365211648), sparse 61% (83856191488), duration 80, read/write 1219/0 MB/s
    INFO: status: 63% (86889529344/136365211648), sparse 63% (86309318656), duration 83, read/write 817/0 MB/s
    INFO: status: 65% (89933873152/136365211648), sparse 65% (89331875840), duration 86, read/write 1014/7 MB/s
    INFO: status: 68% (93587636224/136365211648), sparse 68% (92985004032), duration 89, read/write 1217/0 MB/s
    INFO: status: 71% (97259487232/136365211648), sparse 70% (96656240640), duration 92, read/write 1223/0 MB/s
    INFO: status: 74% (100911218688/136365211648), sparse 73% (100307460096), duration 95, read/write 1217/0 MB/s
    INFO: status: 76% (103736672256/136365211648), sparse 75% (103115829248), duration 98, read/write 941/5 MB/s
    INFO: status: 78% (107457740800/136365211648), sparse 78% (106836385792), duration 101, read/write 1240/0 MB/s
    INFO: status: 81% (110785986560/136365211648), sparse 80% (110162505728), duration 104, read/write 1109/0 MB/s
    INFO: status: 83% (114410586112/136365211648), sparse 83% (113786490880), duration 107, read/write 1208/0 MB/s
    INFO: status: 86% (118096461824/136365211648), sparse 86% (117471854592), duration 110, read/write 1228/0 MB/s
    INFO: status: 88% (121210011648/136365211648), sparse 88% (120570327040), duration 113, read/write 1037/5 MB/s
    INFO: status: 91% (124880289792/136365211648), sparse 91% (124239974400), duration 116, read/write 1223/0 MB/s
    INFO: status: 94% (128542048256/136365211648), sparse 93% (127901220864), duration 119, read/write 1220/0 MB/s
    INFO: status: 96% (132172808192/136365211648), sparse 96% (131531374592), duration 122, read/write 1210/0 MB/s
    INFO: status: 99% (135873036288/136365211648), sparse 99% (135231602688), duration 125, read/write 1233/0 MB/s
    INFO: status: 100% (136365211648/136365211648), sparse 99% (135723773952), duration 126, read/write 492/0 MB/s
    INFO: transferred 136365 MB in 126 seconds (1082 MB/s)
    INFO: archive file size: 294MB
    INFO: Finished Backup of VM 100 (01:02:18)
    INFO: Backup job finished successfully
    TASK OK
    Thank you
     
  2. aderumier

    aderumier Member

    Joined:
    May 14, 2013
    Messages:
    203
    Likes Received:
    18
    do you have enable guest agent, and is guest-agent service running in your vm ?
     
  3. killmasta93

    killmasta93 Member

    Joined:
    Aug 13, 2017
    Messages:
    404
    Likes Received:
    12
    Thanks for the reply, i have the agent running on the webgui but not sure if its really installed as its running pfSense2.3.5 not sure if thats the cause of it?
    https://imgur.com/a/pnUjD

    Thank you
     
  4. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    3,475
    Likes Received:
    317
    if you did not install the guest agent in the vm itself, it does not run, so please do that or deactivate the guest agent on the gui again
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    killmasta93 likes this.
  5. killmasta93

    killmasta93 Member

    Joined:
    Aug 13, 2017
    Messages:
    404
    Likes Received:
    12
    Thanks for the reply, I was wondering if someone else has accomplish on installing the agent on pfSense or FreeBSD?
     
  6. Manny Vazquez

    Manny Vazquez Member

    Joined:
    Jul 12, 2017
    Messages:
    88
    Likes Received:
    1
    Hi, I am looking into this same problem.
    I already have the agent installed as instructed, but I still get the same 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.

    Any solution to this?
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice