Hello,
i have a 2-node proxmox setup and besides different debian-kvm's one w2k3-server (w2k3 guest best practices - check). Now i've discovered that since a week the scheduled backup doesn't run. Since i wasn't there, i'm pretty sure there were no changes made to the setup.
Unfortunately i couldn't find much when searching for "fairsched" and related problems, so i'm hoping someone here could help me.
The backup itself runs at night with:
[TABLE="width: 500"]
[TR]
[TD]Compression:[/TD]
[TD]GZIP[/TD]
[/TR]
[TR]
[TD]Mode:[/TD]
[TD]Stop[/TD]
[/TR]
[TR]
[TD]Include:[/TD]
[TD]only this vm[/TD]
[/TR]
[/TABLE]
The stop-process itself runs fine - the vm does stop, but then the backup immediately fails:
I've already rebooted everything (host and vm) multiple times and migrated the vm so the backup could run on different hosts - still no luck.
The weird thing about this is, when i use "backup now" (store0/stop/gzip) the backup runs fine, so apparently the problem only occurs if it runs scheduled.
Here's my version info:
i have a 2-node proxmox setup and besides different debian-kvm's one w2k3-server (w2k3 guest best practices - check). Now i've discovered that since a week the scheduled backup doesn't run. Since i wasn't there, i'm pretty sure there were no changes made to the setup.
Unfortunately i couldn't find much when searching for "fairsched" and related problems, so i'm hoping someone here could help me.
The backup itself runs at night with:
[TABLE="width: 500"]
[TR]
[TD]Compression:[/TD]
[TD]GZIP[/TD]
[/TR]
[TR]
[TD]Mode:[/TD]
[TD]Stop[/TD]
[/TR]
[TR]
[TD]Include:[/TD]
[TD]only this vm[/TD]
[/TR]
[/TABLE]
The stop-process itself runs fine - the vm does stop, but then the backup immediately fails:
INFO: starting new backup job: vzdump 105 --quiet 1 --mode stop --compress gzip --storage store1
INFO: Starting Backup of VM 105 (qemu)
INFO: status = running
INFO: update VM 105: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: stopping vm
INFO: creating archive '/data/store1/dump/vzdump-qemu-105-2014_11_23-01_00_01.vma.gz'
INFO: starting kvm to execute backup task
unable to create fairsched node
INFO: restarting vm
INFO: vm is online again after 9 seconds
ERROR: Backup of VM 105 failed - start failed: command '/usr/bin/kvm -id 105 -chardev 'socket,id=qmp,path=/var/run/qemu-server/105.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/105.vnc,x509,password -pidfile /var/run/qemu-server/105.pid -daemonize -name ponza -smp 'sockets=2,cores=2' -nodefaults -boot 'menu=on' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -k de -m 4096 -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:49ec7ca2d15' -drive 'file=/data/store0/images/105/vm-105-disk-1.qcow2,if=none,id=drive-ide0,format=qcow2,cache=writethrough,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap105i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=7E:092:57:C3:22,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc-i440fx-1.7' -S' failed: exit code 1
INFO: Backup job finished with errors
TASK ERROR: job errors
I've already rebooted everything (host and vm) multiple times and migrated the vm so the backup could run on different hosts - still no luck.
The weird thing about this is, when i use "backup now" (store0/stop/gzip) the backup runs fine, so apparently the problem only occurs if it runs scheduled.
Here's my version info: