Problems with backing up and boot again

A

Alternativende

Renowned Member
Aug 27, 2015
30
1
73
Hello guys,
i have a really small Debian machine here on Proxmox 5 which won´t back up anymore. Other machines on this server run well.

Here is what i get when i try to backup the machine when its running:

Code: 
Virtual Environment 5.0-23/af4267bf
Virtuelle Maschine 101 ('BAREOS' ) auf Knoten 'PVE01'
Logs
()
INFO: starting new backup job: vzdump 101 --mode stop --node PVE01 --remove 0 --compress lzo --storage BackupBAREOS
INFO: Starting Backup of VM 101 (qemu)
INFO: status = running
INFO: update VM 101: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: BAREOS
INFO: include disk 'virtio0' 'local:101/vm-101-disk-1.qcow2' 64G
INFO: stopping vm
INFO: creating archive '/mnt/pve/BackupBAREOS/dump/vzdump-qemu-101-2017_07_28-11_04_43.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task 'ed27fc2c-6928-4e47-8be3-07640b1228e9'
INFO: resume VM
ERROR: VM 101 not running
INFO: aborting backup job
ERROR: VM 101 not running
INFO: restarting vm
INFO: start failed: org.freedesktop.systemd1.UnitExists: Unit 101.scope already exists.
command 'qm start 101 --skiplock' failed: exit code 255
ERROR: Backup of VM 101 failed - VM 101 not running
INFO: Backup job finished with errors
TASK ERROR: job errors

It shuts down before well and very fast, but it won´t resume and do the actual backup task. But of course im able to start this machine by hand and even with

Code: 
# qm start 101 --skiplock
Failed to stop 101.scope: Unit 101.scope not loaded.

it works. Eventhough he reports the error, the machine starts.

Well i don´t know if it´s a bug or what´s happening here.


101.conf
Code: 
bootdisk: virtio0
cores: 4
ide2: none,media=cdrom
memory: 2048
name: BAREOS
net0: virtio=66:79:67:74:E5:45,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=a3825a96-ad98-4358-b960-700aacbe5309
sockets: 1
virtio0: local:101/vm-101-disk-1.qcow2,size=64G
 
Same problem here.

Code: 
proxmox-ve: 5.0-15 (running kernel: 4.10.15-1-pve) 
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf) 
pve-kernel-4.4.40-1-pve: 4.4.40-82 
pve-kernel-4.4.49-1-pve: 4.4.49-86 
pve-kernel-4.10.15-1-pve: 4.10.15-15 
pve-kernel-4.4.35-1-pve: 4.4.35-77 
pve-kernel-4.4.44-1-pve: 4.4.44-84 
pve-kernel-4.4.67-1-pve: 4.4.67-92 
pve-kernel-4.4.59-1-pve: 4.4.59-87 
libpve-http-server-perl: 2.0-5 
lvm2: 2.02.168-pve2 
corosync: 2.4.2-pve3 
libqb0: 1.0.1-1 
pve-cluster: 5.0-10 
qemu-server: 5.0-12 
pve-firmware: 2.0-2 
libpve-common-perl: 5.0-16 
libpve-guest-common-perl: 2.0-11 
libpve-access-control: 5.0-5 
libpve-storage-perl: 5.0-12 
pve-libspice-server1: 0.12.8-3 
vncterm: 1.5-2 
pve-docs: 5.0-8 
pve-qemu-kvm: 2.9.0-2 
pve-container: 2.0-15 
pve-firewall: 3.0-1 
pve-ha-manager: 2.0-2 
ksm-control-daemon: 1.2-2 
glusterfs-client: 3.8.8-1 
lxc-pve: 2.0.8-3 
lxcfs: 2.0.7-pve2 
criu: 2.11.1-1~bpo90 
novnc-pve: 0.6-4 
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90
 

Attachments

  • 2017-07-30_09-50-53.jpg
    2017-07-30_09-50-53.jpg
    71.3 KB · Views: 13
I got exactly the same problem on Proxmox 5.0.30.
All my scheduled backups doesn't work anymore
if i run manually the command when the vm is already running:
vzdump 755 --storage local --compress lzo --mode stop --remove 0 --node mynode
i get the error
Failed to stop 755.scope: Unit 755.scope not loaded.
And in dmesg i also got this error :
segfault at 10 ip 0000558d6d4b0680 sp 00007f0d474f92f8 error 4 in kvm[558d6cf6d000+7b7000]
I confirm that disk type f the vm is virtio,

I instead you stop your VM yourself before the backup works
qm stop 755
vzdump 755 --storage local --compress lzo --mode stop --remove 0 --node calcovh2017
root@calcovh2017:~# vzdump 755 --storage local --compress lzo --mode stop --remove 0 --node calcovh2017
INFO: starting new backup job: vzdump 755 --compress lzo --remove 0 --storage local --node calcovh2017 --mode stop
INFO: Starting Backup of VM 755 (qemu)
INFO: status = stopped
INFO: update VM 755: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: qgis-ovh.lausanne.ch
INFO: include disk 'virtio0' 'local:755/vm-755-disk-1.qcow2' 150G
INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-755-2017_08_28-08_09_03.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task '7188dac3-2149-43fe-ad8d-a5d55099c73c'
INFO: status: 0% (432603136/161061273600), sparse 0% (20164608), duration 3, read/write 144/137 MB/s
INFO: status: 1% (1647771648/161061273600), sparse 0% (173621248), duration 23, read/write 60/53 MB/s
INFO: status: 2% (3325427712/161061273600), sparse 0% (278073344), duration 44, read/write 79/74 MB/s
etc..

then after that i restart the VM in my script
qm start 755


So the bug seems to be only related to stop/start the VM in the backup script when doing
qm start 755 --skiplock
 
Hi.
I have the same problem but with a VM with an IDE disk.
Can you help me to apply a solution whit this problem?

INFO: starting new backup job: vzdump 112 --remove 0 --mode stop --node proxmox1 --compress lzo --storage backup4tb
INFO: Starting Backup of VM 112 (qemu)
INFO: status = running
INFO: update VM 112: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: W2K8R2-IP246
INFO: include disk 'ide0' 'local:112/vm-112-disk-1.raw' 120G
INFO: stopping vm
INFO: creating archive '/mnt/backup4tb/dump/vzdump-qemu-112-2017_09_10-18_55_29.vma.lzo'
INFO: starting kvm to execute backup task
INFO: restarting vm
INFO: Failed to stop 112.scope: Unit 112.scope not loaded.
INFO: vm is online again after 29 seconds
ERROR: Backup of VM 112 failed - start failed: org.freedesktop.systemd1.UnitExists: Unit 112.scope already exists.
INFO: Backup job finished with errors
TASK ERROR: job errors
 
https://bugzilla.proxmox.com/show_bug.cgi?id=1420
states, that pve-qemu-kvm >= 2.9.0-5 contains the fix

I got same problem on Proxmox 5.1-35 with Virtio disks. This distro has pve-qemu-kvm_2.9.1-2
Seems to be this is not solved, how to avoid this error?

Log:
INFO: starting new backup job: vzdump 100 101 --node pve1 --quiet 1 --mode stop --storage backup1 --compress lzo
INFO: Starting Backup of VM 100 (qemu)
INFO: status = running
INFO: update VM 100: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: LTVIL006
INFO: include disk 'virtio0' 'local:100/vm-100-disk-1.raw' 50G
INFO: include disk 'virtio1' 'local:100/vm-100-disk-2.raw' 100G
INFO: include disk 'efidisk0' 'local:100/vm-100-disk-3.raw' 128K
INFO: stopping vm
INFO: creating archive '/mnt/backup-vm/pve/dump/vzdump-qemu-100-2017_11_01-23_00_01.vma.lzo'
INFO: starting kvm to execute backup task
INFO: restarting vm
INFO: Failed to stop 100.scope: Unit 100.scope not loaded.
INFO: WARNING: Image format was not specified for '/var/lib/vz/images/100/vm-100-disk-3.raw' and probing guessed raw.
INFO: Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
INFO: Specify the 'raw' format explicitly to remove the restrictions.
INFO: vm is online again after 24 seconds
ERROR: Backup of VM 100 failed - start failed: org.freedesktop.systemd1.UnitExists: Unit 100.scope already exists.
 
different issue, fix is on pve-devel.
 
I'm also having a similar issue, version 5.1-41
Code: 
()
INFO: starting new backup job: vzdump 101 --mode stop --storage buffalo --quiet 1 --mailto xxx@xxx.com --mailnotification always --compress lzo --node proxmox
INFO: Starting Backup of VM 101 (qemu)
INFO: status = running
INFO: update VM 101: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: XXX
INFO: include disk 'scsi0' 'local-lvm:vm-101-disk-3' 1650G
INFO: include disk 'scsi1' 'SAS-storage:vm-101-disk-1' 1861G
INFO: stopping vm
INFO: creating archive '/mnt/pve/buffalo/dump/vzdump-qemu-101-2018_05_26-11_47_02.vma.lzo'
INFO: starting kvm to execute backup task
INFO: restarting vm
INFO: Failed to stop 101.scope: Unit 101.scope not loaded.
INFO: vm is online again after 12 seconds
ERROR: Backup of VM 101 failed - start failed: org.freedesktop.systemd1.UnitExists: Unit 101.scope already exists.
INFO: Backup job finished with errors
TASK ERROR: job errors
 
You must log in or register to reply here.
Top Bottom