Have noticed that VM loses it's configuration if backup process fails.
Any ideas how to restore VM config file and prevent PROXMOX from doing such nasty things?
Code:
[COLOR=#000000][FONT=tahoma]INFO: Starting Backup of VM 130 (qemu)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: status = running[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: update VM 130: -lock backup[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: backup mode: snapshot[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: ionice priority: 7[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: creating archive '/mnt/pve/pve_backup/dump/vzdump-qemu-130-2015_05_19-00_15_02.vma.lzo'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: backup contains no disks[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: starting template backup[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: /usr/bin/vma create -v -c /mnt/pve/pve_backup/dump/vzdump-qemu-130-2015_05_19-00_15_02.tmp/qemu-server.conf exec:lzop>/mnt/pve/pve_backup/dump/vzdump-qemu-130-2015_05_19-00_15_02.vma.dat[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]INFO: vma: vma-writer.c:139: vma_writer_add_config: Assertion `len' failed.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]ERROR: Backup of VM 130 failed - command '/usr/bin/vma create -v -c /mnt/pve/pve_backup/dump/vzdump-qemu-130-2015_05_19-00_15_02.tmp/qemu-server.conf 'exec:lzop>/mnt/pve/pve_backup/dump/vzdump-qemu-130-2015_05_19-00_15_02.vma.dat'' failed: got signal 6[/FONT][/COLOR]
Code:
root@pve02A:/etc/pve/nodes/pve01C/qemu-server# ls -alh
total 2.5K
drwxr-x--- 2 root www-data 0 Feb 1 13:31 .
drwxr-x--- 2 root www-data 0 Feb 1 13:31 ..
-rw-r----- 1 root www-data [B] 0[/B] May 19 00:15 130.conf
-rw-r----- 1 root www-data 487 May 19 01:12 136.conf
-rw-r----- 1 root www-data 396 Mar 31 17:16 205.conf
-rw-r----- 1 root www-data 888 Mar 18 16:27 503.conf
-rw-r----- 1 root www-data 294 Mar 18 16:27 504.conf
Code:
root@pve01C:~# pveversion -v
proxmox-ve-2.6.32: not correctly installed (running kernel: 3.10.0-9-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-3.10.0-8-pve: 3.10.0-30
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-3.10.0-9-pve: 3.10.0-33
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-34-pve: 2.6.32-140
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-17
qemu-server: 3.4-5
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1Any ideas how to restore VM config file and prevent PROXMOX from doing such nasty things?
Last edited: