mirror of
https://github.com/Corsinvest/cv4pve-autosnap.git
synced 2026-04-25 17:05:48 +03:00
[GH-ISSUE #11] Snapshots are not deleted automaticaly #10
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cv4pve-autosnap#10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cheechmarino on GitHub (May 31, 2019).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/11
Hi. After latest updates installation from no-subscription repository no snapshots are deleted after "eve4pve-autosnap snap" execution with "keep" parameter enabled. Checked log files and there are only snapshot creation entries, no errors.
On Proxmox machine with enterprise repository everything works like it should.
@franklupo commented on GitHub (May 31, 2019):
Hi,
can you execute with parameter --debug and send me output?
Best regards
@cheechmarino commented on GitHub (May 31, 2019):
root@pmvt2:~# eve4pve-autosnap snap --vmid=2000 --label='daily' --keep=14 --debug
2019-05-31 12:04:19 DEBUG: eve4pve-autosnap 0.1.8
2019-05-31 12:04:19 DEBUG: Command line: snap --vmid=2000 --label=daily --keep=14 --debug
2019-05-31 12:04:19 DEBUG: ------------------------------------------------------------
2019-05-31 12:04:19 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-job-start
2019-05-31 12:04:19 DEBUG: EVE4PVE_AUTOSNAP_VMID: 2000
2019-05-31 12:04:19 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY:
2019-05-31 12:04:19 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily
2019-05-31 12:04:19 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 14
2019-05-31 12:04:19 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 0
2019-05-31 12:04:19 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: -
2019-05-31 12:04:19 DEBUG: ------------------------------------------------------------
2019-05-31 12:04:21 DEBUG: ------------------------------------------------------------
2019-05-31 12:04:21 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-create-pre
2019-05-31 12:04:21 DEBUG: EVE4PVE_AUTOSNAP_VMID: 2000
2019-05-31 12:04:21 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY: qm
2019-05-31 12:04:21 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily
2019-05-31 12:04:21 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 14
2019-05-31 12:04:21 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 0
2019-05-31 12:04:21 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: autodaily190531120419
2019-05-31 12:04:21 DEBUG: ------------------------------------------------------------
VM 2000 - Creating snapshot autodaily190531120419
2019-05-31 12:04:21 DEBUG: qm snapshot 2000 autodaily190531120419 -description 'eve4pve-autosnap'
2019-05-31 12:04:22 DEBUG: return 0
2019-05-31 12:04:22 DEBUG: ------------------------------------------------------------
2019-05-31 12:04:22 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-create-post
2019-05-31 12:04:22 DEBUG: EVE4PVE_AUTOSNAP_VMID: 2000
2019-05-31 12:04:22 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY: qm
2019-05-31 12:04:22 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily
2019-05-31 12:04:22 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 14
2019-05-31 12:04:22 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 0
2019-05-31 12:04:22 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: autodaily190531120419
2019-05-31 12:04:22 DEBUG: ------------------------------------------------------------
2019-05-31 12:04:23 DEBUG: ------------------------------------------------------------
2019-05-31 12:04:23 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-job-end
2019-05-31 12:04:23 DEBUG: EVE4PVE_AUTOSNAP_VMID: 0
2019-05-31 12:04:23 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY:
2019-05-31 12:04:23 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily
2019-05-31 12:04:23 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 14
2019-05-31 12:04:23 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 0
2019-05-31 12:04:23 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: -
2019-05-31 12:04:23 DEBUG: ------------------------------------------------------------
2019-05-31 12:04:23 DEBUG: Execution: 4 sec.
@franklupo commented on GitHub (May 31, 2019):
execute
and attach output.
@cheechmarino commented on GitHub (May 31, 2019):
root@pmvt2:~# qm listsnapshot 2000
-> autodaily190516000003 2019-05-16 00:00:06 eve4pve-autosnap
-> autodaily190517000003 2019-05-17 00:00:06 eve4pve-autosnap
-> autodaily190518000003 2019-05-18 00:00:06 eve4pve-autosnap
-> autodaily190519000003 2019-05-19 00:00:06 eve4pve-autosnap
-> autodaily190520000003 2019-05-20 00:00:06 eve4pve-autosnap
-> autodaily190521000003 2019-05-21 00:00:06 eve4pve-autosnap
-> autodaily190522000003 2019-05-22 00:00:06 eve4pve-autosnap
-> autodaily190523000003 2019-05-23 00:00:06 eve4pve-autosnap
-> autodaily190524000003 2019-05-24 00:00:06 eve4pve-autosnap
-> autodaily190525000003 2019-05-25 00:00:06 eve4pve-autosnap
-> autodaily190526000003 2019-05-26 00:00:06 eve4pve-autosnap
-> autodaily190527000003 2019-05-27 00:00:06 eve4pve-autosnap
-> autodaily190528000003 2019-05-28 00:00:06 eve4pve-autosnap
-> autodaily190529000003 2019-05-29 00:00:06 eve4pve-autosnap
-> autodaily190530000003 2019-05-30 00:00:06 eve4pve-autosnap
-> autodaily190531000003 2019-05-31 00:00:06 eve4pve-autosnap
-> autodaily190531063836 2019-05-31 06:38:39 eve4pve-autosnap
-> autodaily190531120419 2019-05-31 12:04:22 eve4pve-autosnap
-> current You are here!
@franklupo commented on GitHub (May 31, 2019):
Hi the problem is the change format of output.
can add output command "pveversion"
@cheechmarino commented on GitHub (May 31, 2019):
pve-manager/5.4-6/aa7856c5 (running kernel: 4.15.18-15-pve)
@franklupo commented on GitHub (May 31, 2019):
ok found problem create fix
best regards
@cheechmarino commented on GitHub (May 31, 2019):
ThankYou!!!
@franklupo commented on GitHub (May 31, 2019):
Please check new version if working,
Let me know if there are any problems.
Best regards
@cheechmarino commented on GitHub (May 31, 2019):
Hi. Can confirm that new version is working on latest Proxmox no-subscription updates.
Thank You very much!!!
@franklupo commented on GitHub (May 31, 2019):
Pferfext
@datacenter1 commented on GitHub (Jun 12, 2019):
Hi
I have the same issue but 0.19 didn't fix it, started after the last reboot
Still working in other nodes with same Proxmox versión but without reboot yet
Thank you
@altoch commented on GitHub (Jun 12, 2019):
I rebooted a host, and seems the crontab eve4pve-autosnap file got reset to default.
So it's empty file no programmed tasks
Quick solution, create your own crontab file
After launching autosnap command, throws this error:
eve4pve-autosnap snap --vmid=102 --label='daily' --keep=3
And then old snapshots are not deleted
VM 102 - Creating snapshot autodaily190613005023
Use of uninitialized value $root in hash element at /usr/share/perl5/PVE/CLI/qm. pm line 949.
Use of uninitialized value $root in printf at /usr/share/perl5/PVE/CLI/qm.pm lin e 960.
Use of uninitialized value $root in hash element at /usr/share/perl5/PVE/CLI/qm. pm line 949.
Use of uninitialized value $root in printf at /usr/share/perl5/PVE/CLI/qm.pm lin e 960.
Same here
@franklupo commented on GitHub (Jun 14, 2019):
Hi,
can add output "qm listsnapshot 100" ?
Best regards
@altoch commented on GitHub (Jun 14, 2019):
Here you have, notice that the previous command was runned with --vmid=102
root@~# qm listsnapshot 100-> automonthly190601040003 2019-06-01 04:00:05 eve4pve-autosnap-> autoweekly190602030003 2019-06-02 03:00:05 eve4pve-autosnap-> autoweekly190609030003 2019-06-09 03:00:06 eve4pve-autosnap-> autodaily190613004446 2019-06-13 00:44:49 eve4pve-autosnap-> autodaily190613020005 2019-06-13 02:00:08 eve4pve-autosnap-> autodaily190614020004 2019-06-14 02:00:07 eve4pve-autosnap-> current You are here!`
@franklupo commented on GitHub (Jun 14, 2019):
Can redirect oupout to file and add file?
Best regards
@woody4165 commented on GitHub (Sep 11, 2019):
Hi @franklupo
I'm on version 0.1.8
how can I upgrade to 0.1.9 since I'm having the same issue here, the snapshot are not deleted automatically?
I have the tool installed directly on the Proxmox instance.
Thanks
@franklupo commented on GitHub (Sep 11, 2019):
I,
The bash versions are no longer supported.
Download the latest versions that use the native API.
Best reagrds
@woody4165 commented on GitHub (Sep 11, 2019):
In this case I need to install on another machine other than proxmox?
@franklupo commented on GitHub (Sep 11, 2019):
It is possible to install on the same machine.
The new autosnap works on clusters does not need to be installed on the various machines of a claster.
It can be installed on a Windows / Linux / Mac OS machine and execute a schedule.
It works the same way.
@woody4165 commented on GitHub (Sep 12, 2019):
Grazie @franklupo
I thought it works only outside Proxmox as it's written in the main page:
"In this version the tool works outside the Proxmox VE host using the API."
So, to uninstall previous version (eve4pve-autosnap) what should I do?
I see that the scheduling is in /etc/pve/eve/autosnap/eve4pve-autosnap.cron
Thanks
@franklupo commented on GitHub (Sep 12, 2019):
HI,
apt-get remove eve4pve-autosnap
remove link eve4pve-autosnap.cron
Best regards
@woody4165 commented on GitHub (Sep 12, 2019):
Thanks
Really strange that I get
and if if try to find eve4pve-autosnap I get
should I remove it manually?
Sorry for all these questions!
@franklupo commented on GitHub (Sep 12, 2019):
No problem.
Consider a donation to support the project.
Best regards