Backup - Problem Version 5.0-30

S

Sebastian L.

New Member
Aug 25, 2017
18
1
1
34
Hallo,
wir nutzen derzeit die Proxmox Version: 5.0-30.
Wir verwenden als VMs Linux und Windows.
Aktuell haben wir arge Probleme beim Backup.
Aktuell erhalten wir die Fehlermeldungen:

INFO: start failed: org.freedesktop.systemd1.UnitExists: Unit 100.scope already exists.
command 'qm start 100 --skiplock' failed: exit code 255
ERROR: Backup of VM 100 failed - VM 100 not running

oder auch


NFO: VM quit/powerdown failed
ERROR: Backup of VM 105 failed - command 'qm shutdown 105 --skiplock --keepActive --timeout 600' failed: exit code 255
INFO: Backup job finished with errors


Windows läuft mit IDE Platten und LInux luft mit VIRTIO.

Der Proxmox Agent ist auf jeder VM installiert und auch über den PING - Test erreichbar.

Hoffe jemand kann helfen.
 
Hi Udo,
erstmal zu Linux, das ACPI ist aktiv. Trotzdem kommt bei Stop / Backup folgendes und ich weiß nicht warum das kommt....

INFO: creating archive '/mnt/storage/100/dump/vzdump-qemu-100-2017_08_30-20_22_59.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task '28183c98-40e9-45dd-b9ef-5aaba5cf6538'
INFO: resume VM
ERROR: VM 100 not running
INFO: aborting backup job
ERROR: VM 100 not running
INFO: restarting vm
INFO: start failed: org.freedesktop.systemd1.UnitExists: Unit 100.scope already exists.
command 'qm start 100 --skiplock' failed: exit code 255
ERROR: Backup of VM 100 failed - VM 100 not running
INFO: Backup job finished with errors
TASK ERROR: job errors
TASK ERROR: start failed: org.freedesktop.systemd1.UnitExists: Unit 100.scope already exists.
 
Hi Fabian,
ja es ist sicher dieser Bug..
Ich sehe du hast einen fix gepostet. Wie muss man diesen anwenden? :S
Kannst du es bitte kurz beschreiben, will es ungern zerschießen, mein Proxmox.
 
mögliche workarounds sind:
  • nicht stop-mode backup, sondern falls möglich snapshot- oder suspend mode, ODER
  • manuell herunterfahren, stop-mode backup machen, wieder starten, ODER
  • die disks statt mit virtio-block (virtioN) mit virtio-scsi (scsiN und scsihw entsprechend gesetzt) konfigurieren
pakete mit fix wird es anfang nächster woche geben
 
Hallo,
ich habe nun das Update gemacht und anschließend den PVE1 auf reboot per Proxmox GUI gesetzt. Nach dem Reboot habe ich versucht erneut den BAckupjob über STOP - Mode auszuführen.

Erneut dieser Fehler:
INFO: starting new backup job: vzdump 100 --compress lzo --storage backup_100 --node pve1 --mode stop --remove 0
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: srv4
INFO: include disk 'virtio0' 'local-lvm:vm-100-disk-1' 80G
INFO: stopping vm
INFO: creating archive '/mnt/storage/100/dump/vzdump-qemu-100-2017_09_09-10_18_45.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task 'ddc9b19d-971a-49e8-a40e-68f114c2737e'
INFO: resume VM
ERROR: VM 100 not running
INFO: aborting backup job
ERROR: VM 100 not running
INFO: restarting vm
INFO: start failed: org.freedesktop.systemd1.UnitExists: Unit 100.scope already exists.
command 'qm start 100 --skiplock' failed: exit code 255
ERROR: Backup of VM 100 failed - VM 100 not running
INFO: Backup job finished with errors
TASK ERROR: job errors
 
works as expected here.. can you verify the installed version via pveversion -v?
 
Hello Fabian, sure.

Here you can see output of pvevefsion -v

Code: 
proxmox-ve: 5.0-21 (running kernel: 4.10.17-3-pve)
pve-manager: 5.0-31 (running version: 5.0-31/27769b1f)
pve-kernel-4.10.17-2-pve: 4.10.17-20
pve-kernel-4.10.17-3-pve: 4.10.17-21
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-4
pve-container: 2.0-15
pve-firewall: 3.0-2
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-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.11-pve17~bpo90

It seems that the problem occur because of
Code: 
INFO: start failed: org.freedesktop.systemd1.UnitExists: Unit 100.scope already exists.

Or did my upgrade not upgrade kernel? I restart PVE 2 times... Maybe need some command? If yes which command?

Hope you can help.
 
you still have pve-qemu-kvm 2.9.0-4 installed..
 
Hello Fabian,
I try again... but
Code: 
root@pve1:~# apt-get update
Get:1 http://security.debian.org stretch/updates InRelease [62.9 kB]
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
Hit:3 http://ftp.de.debian.org/debian stretch Release
Hit:5 http://download.proxmox.com/debian stretch InRelease
Fetched 62.9 kB in 3s (19.8 kB/s)
Reading package lists... Done
root@pve1:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  pve-qemu-kvm
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Why he kept back pve-qemu-kvm? How I can do it?

I do now
Code: 
root@pve1:~# apt-get install pve-qemu-kvm

And it update and seems now ok:
Code: 
root@pve1:~# pveversion -v
proxmox-ve: 5.0-21 (running kernel: 4.10.17-3-pve)
pve-manager: 5.0-31 (running version: 5.0-31/27769b1f)
pve-kernel-4.10.17-2-pve: 4.10.17-20
pve-kernel-4.10.17-3-pve: 4.10.17-21
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-5
pve-container: 2.0-15
pve-firewall: 3.0-2
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-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.11-pve17~bpo90

But why it keep back?
 
Sebastian L. said:
Hello Fabian,
I try again... but
Code: 
root@pve1:~# apt-get upgrade
...

But why it keep back?[/QUOTE]

Because you run the wrong command.

=> never run "apt-get upgrade", this will break your host in most cases.

Follow our upgrade guide on:

https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_5.x_to_latest_5.0
Click to expand...
 
Hello,
normally we do updtae via GUI so as I understand we should now each time only do the 2 commands for update and uograde:

1. command:
Code: 
apt update

2. command
Code: 
apt dist-upgrade

last step
Code: 
reboot

right?
Or how? :S
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back