starred/cv4pve-admin
1
0
Fork 0
mirror of https://github.com/Corsinvest/cv4pve-admin.git synced 2026-04-25 12:55:57 +03:00
Code Issues 4 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #129] Snapshots causing VM to crash and become unresponsive #53

New issue
Closed
opened 2026-02-26 17:37:03 +03:00 by kerem · 4 comments
kerem commented 2026-02-26 17:37:03 +03:00
Owner
Copy link

Originally created by @greavette on GitHub (Mar 6, 2025).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-admin/issues/129

Hello,

I've been using cv4pve-admin for about a year now, and it's been great to have the ability to schedule my snapshots on some critical VMs. I've had issues in the past 2 months with my Windows Server 2019 running SQL Server (database) where, during the snapshot, my VM becomes unresponsive, and my only recourse is to reboot the VM. I've looked in my PVE System Logs, and I can see the following events occurring during the snapshot:

Mar 03 03:52:51 swasprox07 pvestatd[3664]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - unable to connect to VM 201 qmp socket - timeout after 51 retries
Mar 03 03:52:58 swasprox07 pvestatd[3664]: HostedSymmcomPBS: error fetching datastores - 500 Can't connect to pbs.symm.cloud:41812 (Connection timed out)
Mar 03 03:52:58 swasprox07 pvestatd[3664]: status update time (15.731 seconds)
Mar 03 03:53:02 swasprox07 pvedaemon[1088979]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - unable to connect to VM 201 qmp socket - timeout after 51 retries
Mar 03 03:53:02 swasprox07 pvedaemon[1214971]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - unable to connect to VM 201 qmp socket - timeout after 51 retries
Mar 03 03:53:05 swasprox07 pvescheduler[1221042]: could not update job state, skipping - no such task
Mar 03 03:53:06 swasprox07 pvestatd[3664]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - unable to connect to VM 201 qmp socket - timeout after 51 retries
Mar 03 03:53:12 swasprox07 pvedaemon[1045959]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - unable to connect to VM 201 qmp socket - timeout after 51 retries
Mar 03 03:53:14 swasprox07 pvestatd[3664]: HostedSymmcomPBS: error fetching datastores - 500 Can't connect to pbs.symm.cloud:41812 (Connection timed out)
Mar 03 03:53:14 swasprox07 pvestatd[3664]: status update time (15.747 seconds)
Mar 03 03:53:18 swasprox07 pvedaemon[1045959]: worker exit

I've confirmed that if I turn off snapshots, my VM doesn't have this issue.

My Auto Snapshot job is using 'Vm Status', 'Only Runs', I keep 8 Snapshots.

Has anyone else recorded this before? I'm searching the Proxmox Forums as well and I'm reaching out to PVE support to see if there are other reasons for this to occur.

Any advice you can provide me would be greatly appreciated.

Thank you.

Originally created by @greavette on GitHub (Mar 6, 2025). Original GitHub issue: https://github.com/Corsinvest/cv4pve-admin/issues/129 Hello, I've been using cv4pve-admin for about a year now, and it's been great to have the ability to schedule my snapshots on some critical VMs. I've had issues in the past 2 months with my Windows Server 2019 running SQL Server (database) where, during the snapshot, my VM becomes unresponsive, and my only recourse is to reboot the VM. I've looked in my PVE System Logs, and I can see the following events occurring during the snapshot: ``` Mar 03 03:52:51 swasprox07 pvestatd[3664]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - unable to connect to VM 201 qmp socket - timeout after 51 retries Mar 03 03:52:58 swasprox07 pvestatd[3664]: HostedSymmcomPBS: error fetching datastores - 500 Can't connect to pbs.symm.cloud:41812 (Connection timed out) Mar 03 03:52:58 swasprox07 pvestatd[3664]: status update time (15.731 seconds) Mar 03 03:53:02 swasprox07 pvedaemon[1088979]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - unable to connect to VM 201 qmp socket - timeout after 51 retries Mar 03 03:53:02 swasprox07 pvedaemon[1214971]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - unable to connect to VM 201 qmp socket - timeout after 51 retries Mar 03 03:53:05 swasprox07 pvescheduler[1221042]: could not update job state, skipping - no such task Mar 03 03:53:06 swasprox07 pvestatd[3664]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - unable to connect to VM 201 qmp socket - timeout after 51 retries Mar 03 03:53:12 swasprox07 pvedaemon[1045959]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - unable to connect to VM 201 qmp socket - timeout after 51 retries Mar 03 03:53:14 swasprox07 pvestatd[3664]: HostedSymmcomPBS: error fetching datastores - 500 Can't connect to pbs.symm.cloud:41812 (Connection timed out) Mar 03 03:53:14 swasprox07 pvestatd[3664]: status update time (15.747 seconds) Mar 03 03:53:18 swasprox07 pvedaemon[1045959]: worker exit ``` I've confirmed that if I turn off snapshots, my VM doesn't have this issue. My Auto Snapshot job is using 'Vm Status', 'Only Runs', I keep 8 Snapshots. Has anyone else recorded this before? I'm searching the Proxmox Forums as well and I'm reaching out to PVE support to see if there are other reasons for this to occur. Any advice you can provide me would be greatly appreciated. Thank you.
kerem closed this issue 2026-02-26 17:37:03 +03:00
kerem commented 2026-02-26 17:37:03 +03:00
Author
Owner
Copy link

@franklupo commented on GitHub (Mar 6, 2025):

Hi,
qemu-agent is installed correctly?
But do you save memory?
Have you tried to do it from the proxmox ve web interface?
What does the snapshot lof on Promxoxm VE say?

bets regards

<!-- gh-comment-id:2704256950 --> @franklupo commented on GitHub (Mar 6, 2025): Hi, qemu-agent is installed correctly? But do you save memory? Have you tried to do it from the proxmox ve web interface? What does the snapshot lof on Promxoxm VE say? bets regards
kerem commented 2026-02-26 17:37:03 +03:00
Author
Owner
Copy link

@greavette commented on GitHub (Mar 8, 2025):

Hello, and thank you for this reply!

Just to confirm...I'm not throwing any shade at cv4pve-admin at all for this issue I'm having. It's a snapshot issue. But this community is very knowledgable and I thought you may have seen this before.

Does 'Vm Status' mean that I'm saving memory?
I've taken manual snapshots at various/random times, and I have not noticed my VM becoming unresponsive. It seems to occur only at 3:50 a.m.

I don't see any log information on the snapshot log that indicates an issue. The PVE syslog is where I see the issue (which I pasted in my original post).

Yes, my qemu-agent is installed correctly, updated and is working properly.

Thank you.

<!-- gh-comment-id:2708470735 --> @greavette commented on GitHub (Mar 8, 2025): Hello, and thank you for this reply! Just to confirm...I'm not throwing any shade at cv4pve-admin at all for this issue I'm having. It's a snapshot issue. But this community is very knowledgable and I thought you may have seen this before. Does 'Vm Status' mean that I'm saving memory? I've taken manual snapshots at various/random times, and I have not noticed my VM becoming unresponsive. It seems to occur only at 3:50 a.m. I don't see any log information on the snapshot log that indicates an issue. The PVE syslog is where I see the issue (which I pasted in my original post). Yes, my qemu-agent is installed correctly, updated and is working properly. Thank you.
kerem commented 2026-02-26 17:37:03 +03:00
Author
Owner
Copy link

@franklupo commented on GitHub (Mar 10, 2025):

HI,
I think it is a problem of Proxmox VE and filesystem.
We call Proxmox VE API.
Could it be a ZFS problem?

https://forum.proxmox.com/threads/qmp-command-query-proxmox-support-failed.117246/
https://forum.proxmox.com/threads/snapshot-causes-vm-to-become-unresponsive.153483/page-4

Bets regards

<!-- gh-comment-id:2710109672 --> @franklupo commented on GitHub (Mar 10, 2025): HI, I think it is a problem of Proxmox VE and filesystem. We call Proxmox VE API. Could it be a ZFS problem? https://forum.proxmox.com/threads/qmp-command-query-proxmox-support-failed.117246/ https://forum.proxmox.com/threads/snapshot-causes-vm-to-become-unresponsive.153483/page-4 Bets regards
kerem commented 2026-02-26 17:37:03 +03:00
Author
Owner
Copy link

@franklupo commented on GitHub (Mar 24, 2025):

news?

<!-- gh-comment-id:2747158272 --> @franklupo commented on GitHub (Mar 24, 2025): news?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
gh-pages
feat/vm-jolly-field
v2.0.0
v2.0.0-rc6
v2.0.0-rc5
v2.0.0-rc4
v2.0.0-rc3
v2.0.0-rc2
v2.0.0-rc1
v1.3.1
v1.3.0
v1.2.0
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v1.0.0-rc.3
v1.0.0-rc.2
v1.0.0-rc.1
v0.0.7-beta
v0.0.6-beta
v0.0.5-beta
v0.0.4-beta
v0.0.3-beta
v0.0.2-beta
v0.0.1-beta
Labels
Clear labels   
bug

   
bug

   
enhancement

   
feedback

   
pull-request

Mirrored from GitHub Pull Request

No labels
bug
bug
enhancement
feedback
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cv4pve-admin#53
No description provided.