search

Corsinvest / cv4pve-autosnap

Automatic snapshot tool for Proxmox VE
https://www.corsinvest.it/cv4pve
GNU General Public License v3.0
402 stars 49 forks source link

Autosnap does nothing #3

Closed mgiammarco closed 6 years ago

mgiammarco commented 6 years ago

Hello, I have installed autosnap in a licensed proxmox 4.4. The command:

eve4pve-autosnap snap --vmid=all --label='daily' --keep=10

gives no output

The command:

eve4pve-autosnap snap --vmid=104 --label='daily' --keep=10

gives: ERROR: VM 104 - Unknown tecnology

What can I do? Thanks, Mario

mgiammarco commented 6 years ago

I am using ceph filesystem

franklupo commented 6 years ago

Hi, the vm run in same machine on proxmox?

best regards

mgiammarco commented 6 years ago

It is a cluster, I have tried to add autosnap to all hosts. In another installation it works. Mario

2017-10-06 11:22 GMT+02:00 Daniele Corsini notifications@github.com:

Hi, the vm run in same machine on proxmox?

best regards

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/EnterpriseVE/eve4pve-autosnap/issues/3#issuecomment-334704185, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIUFqolN7bSXIBQf7MWDSiT_tp7Icf4ks5spfFRgaJpZM4PwG3o .

franklupo commented 6 years ago

Ciao Mario, questo script lavora solo sulle VM/CT in esecuzione sull'host in esecuzione.

Daniele

mgiammarco commented 6 years ago

Ciao, si l'ho installato in due cluster per provarlo su tutti i server dei due cluster. In un cluster funziona: su ogni server fa lo snapshot delle macchine che girano su quel server. Sull'altro da quel errore in tutti i server di quel cluster. Mario

2017-10-08 14:03 GMT+02:00 Daniele Corsini notifications@github.com:

Ciao Mario, questo script lavora solo sulle VM/CT in esecuzione sull'host in esecuzione.

Daniele

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/EnterpriseVE/eve4pve-autosnap/issues/3#issuecomment-335002015, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIUFo2CSdrF2R3R2bqmDvpzQ-Y537Tvks5sqLojgaJpZM4PwG3o .

franklupo commented 6 years ago

Ciao, che parametri usi per la command line? Prova ad eseguirlo aggiungendo --debug alla command line e allega risultato.

Grazie

franklupo commented 6 years ago

Guarda nuova versione con configurazione cluster

mgiammarco commented 6 years ago

Scusa il ritardo ma purtroppo il caso non è più riproducibile perché ho riavviato la macchina nel frattempo e ora va. Piuttosto in un altro cluster 4.4 dove lo sto provando ho messo eve4pve-barc eve4pve-autosnap e i backup normali e ora vedo che si stanno pestando i piedi. Nella gui sezione snapshots vedo un sacco di auto-snapshots che giustamente da cli non vedo più in quanto dovevano essere cancellati per rispettare il limite di 3. Però vedo un sacco di errori di vm locked e infatti né i backup normali né quelli di barc sono quotidiani. Come posso debuggare? Stavolta non riavvio, Mario

2017-10-08 14:03 GMT+02:00 Daniele Corsini notifications@github.com:

Ciao Mario, questo script lavora solo sulle VM/CT in esecuzione sull'host in esecuzione.

Daniele

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/EnterpriseVE/eve4pve-autosnap/issues/3#issuecomment-335002015, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIUFo2CSdrF2R3R2bqmDvpzQ-Y537Tvks5sqLojgaJpZM4PwG3o .

franklupo commented 6 years ago

Ciao, --debug visualizza debug completo.

Fammi sapere

grazie

mgiammarco commented 6 years ago

Ecco l'output: eve4pve-autosnap snap --vmid=all --label='daily' --keep=3 --vmstate --debug 2017-10-27 09:31:30 DEBUG: eve4pve-autosnap 0.1.6 2017-10-27 09:31:30 DEBUG: Command line: snap --vmid=all --label=daily --keep=3 --vmstate --debug 2017-10-27 09:31:30 DEBUG:

2017-10-27 09:31:30 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-job-start 2017-10-27 09:31:30 DEBUG: EVE4PVE_AUTOSNAP_VMID: 0 2017-10-27 09:31:30 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY: 2017-10-27 09:31:30 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily 2017-10-27 09:31:30 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 3 2017-10-27 09:31:30 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 1 2017-10-27 09:31:30 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: - 2017-10-27 09:31:30 DEBUG:

VM 100 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent 2017-10-27 09:31:32 DEBUG:

2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-create-pre 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_VMID: 100 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY: qm 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 3 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 1 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: autodaily171027093130 2017-10-27 09:31:32 DEBUG:

VM 100 - Creating snapshot autodaily171027093130 2017-10-27 09:31:32 DEBUG: qm snapshot 100 autodaily171027093130 -description 'eve4pve-autosnap' --vmstate you can't take a snapshot if it's a template ERROR: qm snapshot 100 autodaily171027093130 -description 'eve4pve-autosnap' --vmstate 2017-10-27 09:31:32 DEBUG: return 255 2017-10-27 09:31:32 DEBUG:

2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-create-abort 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_VMID: 100 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY: qm 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 3 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 1 2017-10-27 09:31:32 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: autodaily171027093130 2017-10-27 09:31:32 DEBUG:

ERROR: VM 100 - Create snapshot autodaily171027093130 VM 101 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent 2017-10-27 09:31:34 DEBUG:

2017-10-27 09:31:34 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-create-pre 2017-10-27 09:31:34 DEBUG: EVE4PVE_AUTOSNAP_VMID: 101 2017-10-27 09:31:34 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY: qm 2017-10-27 09:31:34 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily 2017-10-27 09:31:34 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 3 2017-10-27 09:31:34 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 1 2017-10-27 09:31:34 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: autodaily171027093130 2017-10-27 09:31:34 DEBUG:

VM 101 - Creating snapshot autodaily171027093130 2017-10-27 09:31:34 DEBUG: qm snapshot 101 autodaily171027093130 -description 'eve4pve-autosnap' --vmstate VM is locked (snapshot-delete) ERROR: qm snapshot 101 autodaily171027093130 -description 'eve4pve-autosnap' --vmstate 2017-10-27 09:31:35 DEBUG: return 255 2017-10-27 09:31:35 DEBUG:

2017-10-27 09:31:35 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-create-abort 2017-10-27 09:31:35 DEBUG: EVE4PVE_AUTOSNAP_VMID: 101 2017-10-27 09:31:35 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY: qm 2017-10-27 09:31:35 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily 2017-10-27 09:31:35 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 3 2017-10-27 09:31:35 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 1 2017-10-27 09:31:35 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: autodaily171027093130 2017-10-27 09:31:35 DEBUG:

ERROR: VM 101 - Create snapshot autodaily171027093130 2017-10-27 09:31:36 DEBUG:

2017-10-27 09:31:36 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-create-pre 2017-10-27 09:31:36 DEBUG: EVE4PVE_AUTOSNAP_VMID: 103 2017-10-27 09:31:36 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY: qm 2017-10-27 09:31:36 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily 2017-10-27 09:31:36 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 3 2017-10-27 09:31:36 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 1 2017-10-27 09:31:36 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: autodaily171027093130 2017-10-27 09:31:36 DEBUG:

VM 103 - Creating snapshot autodaily171027093130 2017-10-27 09:31:36 DEBUG: qm snapshot 103 autodaily171027093130 -description 'eve4pve-autosnap' --vmstate VM is locked (snapshot-delete) ERROR: qm snapshot 103 autodaily171027093130 -description 'eve4pve-autosnap' --vmstate 2017-10-27 09:31:37 DEBUG: return 255 2017-10-27 09:31:37 DEBUG:

2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-create-abort 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_VMID: 103 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY: qm 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 3 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 1 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: autodaily171027093130 2017-10-27 09:31:37 DEBUG:

ERROR: VM 103 - Create snapshot autodaily171027093130 2017-10-27 09:31:37 DEBUG:

2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_PHASE: snap-job-end 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_VMID: 0 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_VMTECNOLOGY: 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_LABEL: daily 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_KEEP: 3 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_VMSTATE: 1 2017-10-27 09:31:37 DEBUG: EVE4PVE_AUTOSNAP_SNAP_NAME: - 2017-10-27 09:31:37 DEBUG:

2017-10-27 09:31:37 DEBUG: Execution: 7 sec.

2017-10-24 23:12 GMT+02:00 Daniele Corsini notifications@github.com:

Ciao, --debug visualizza debug completo.

Fammi sapere

grazie

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/EnterpriseVE/eve4pve-autosnap/issues/3#issuecomment-339133202, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIUFsIJcMiicRCoA5UGBIPiSLszXSZDks5svlLLgaJpZM4PwG3o .

mgiammarco commented 6 years ago

Se do qm unlock su tutte le macchine poi lo snapshot riparte. Il problema è che proxmox nell'elenco degli snapshot continua a mostrare quelli cancellati ed è probabilmente lui che mette il lock sulle macchine. Oppure il backup. Oppure barc. Non so, la domanda è: è possibile farli girare tutti e 3 assieme sullo stesso cluster? Grazie, Mario

2017-10-24 23:12 GMT+02:00 Daniele Corsini notifications@github.com:

Ciao, --debug visualizza debug completo.

Fammi sapere

grazie

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/EnterpriseVE/eve4pve-autosnap/issues/3#issuecomment-339133202, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIUFsIJcMiicRCoA5UGBIPiSLszXSZDks5svlLLgaJpZM4PwG3o .

franklupo commented 6 years ago

Il problema può essere che le macchine siano bloccata da un processo e gli altri tentano di eseguire. Forse un problema di esecuzione contemporanea.

Non so, la domanda è: è possibile farli girare tutti e 3 assieme sullo stesso cluster?

Direi di no tutti bloccano