Windows 2003 VM stops unexpectedly during backup

J

jazzl0ver

Renowned Member
Mar 6, 2013
69
1
73
Hi,

Sometimes the VM stops right after the backup is started.

# pveversion -v
proxmox-ve-2.6.32: not correctly installed (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-13 (running version: 3.4-13/4c745357)
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-37-pve: 2.6.32-150
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-3
pve-cluster: 3.0-19
qemu-server: 3.4-8
pve-firmware: 1.1-5
libpve-common-perl: 3.0-26
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-34
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-25
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

VM is Windows 2003 Web Edition SP2 x86
#ide0%3A LVM-Storage%3A111/vm-dentc.raw,size=76G
balloon: 512
bootdisk: ide0
cores: 2
ide0: LVM-Storage:111/vm-111-disk-1.raw,format=raw,size=76320M
ide2: none,media=cdrom
memory: 2048
name: vm-dentc
net0: e1000=76:5E:AC:00:18:45,bridge=vmbr12
onboot: 1
ostype: wxp
smbios1: uuid=4eeaa765-8050-4232-b126-06432ed65f06
sockets: 1

- Windows's system.log just says about unexpected shutdown
- Proxmox logs show nothing but vzdump error about not running VM
Jun 15 00:30:01 vm-box-4 /USR/SBIN/CRON[378489]: (root) CMD (vzdump 111 --quiet 1 --mailnotification failure --mailto root@mydom.com --mode snapshot --compress lzo
Jun 15 00:30:02 vm-box-4 vzdump[378490]: <root@pam> starting task UPID:vm-box-4:0005C68D:039C116D:5760775A:vzdump::root@pam:
Jun 15 00:30:02 vm-box-4 vzdump[378509]: INFO: starting new backup job: vzdump 111 --mailnotification failure --quiet 1 --mode snapshot --mailto root@mydom.com --c
Jun 15 00:30:02 vm-box-4 vzdump[378509]: INFO: Starting Backup of VM 111 (qemu)
Jun 15 00:30:02 vm-box-4 qm[378514]: <root@pam> update VM 111: -lock backup
Jun 15 00:30:08 vm-box-4 /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing
Jun 15 00:30:18 vm-box-4 /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing
Jun 15 00:30:29 vm-box-4 kernel: vmbr12: port 4(tap111i0) entering disabled state
Jun 15 00:30:29 vm-box-4 kernel: vmbr12: port 4(tap111i0) entering disabled state
Jun 15 00:30:30 vm-box-4 vzdump[378509]: VM 111 qmp command failed - VM 111 not running
Jun 15 00:30:30 vm-box-4 vzdump[378509]: VM 111 qmp command failed - VM 111 not running
Jun 15 00:30:31 vm-box-4 vzdump[378509]: ERROR: Backup of VM 111 failed - VM 111 not running
Jun 15 00:30:31 vm-box-4 vzdump[378509]: INFO: Backup job finished with errors
Jun 15 00:30:31 vm-box-4 vzdump[378509]: job errors

INFO: starting new backup job: vzdump 111 --mailnotification failure --quiet 1 --mode snapshot --mailto root@mydom.com --compress lzo --storage trendy-images
INFO: Starting Backup of VM 111 (qemu)
INFO: status = running
INFO: update VM 111: -lock backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/trendy-images/dump/vzdump-qemu-111-2016_06_15-00_30_02.vma.lzo'
INFO: started backup task '4f4cf869-c68d-407e-b018-42e8c9db29d9'
INFO: status: 0% (250871808/80027320320), sparse 0% (2609152), duration 3, 83/82 MB/s
INFO: status: 1% (812318720/80027320320), sparse 0% (8437760), duration 9, 93/92 MB/s
ERROR: VM 111 not running
INFO: aborting backup job
ERROR: VM 111 not running
ERROR: Backup of VM 111 failed - VM 111 not running
INFO: Backup job finished with errors
TASK ERROR: job errors

What else can I check? Any help is appreciated.
 
jazzl0ver said:
What else can I check? Any help is appreciated.
Click to expand...

You run a very outdated system, please update at least to latest 3.4 and test again.

And consider upgrading to latest 4.x., the 3.x support will end soon.
 
tom said:
You run a very outdated system, please update at least to latest 3.4 and test again.

And consider upgrading to latest 4.x., the 3.x support will end soon.
Click to expand...
Hi tom,

Thanks for the reply!

I'm wondering why you're saying "very outdated system", since there're no pending updates for Proxmox itself, just some system files:
upload_2016-6-15_17-17-28.png

Anyway, of course, I'll give it a try.

I wouldn't like to upgrade to version 4.x at the moment, since it lacks support of several things we use.
 
tom said:
your pveversion -v show outdated packages:

check against the list on:

http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.4
Click to expand...
Here is the diff between my packages and the list in the wiki:
root@vm-box-4:~# diff cur new
1c1
< proxmox-ve-2.6.32: not correctly installed (running kernel: 2.6.32-37-pve)
---
> proxmox-ve-2.6.32: 3.4-175 (running kernel: 2.6.32-46-pve)
3,5c3
< pve-kernel-2.6.32-33-pve: 2.6.32-138
< pve-kernel-2.6.32-37-pve: 2.6.32-150
< pve-kernel-2.6.32-34-pve: 2.6.32-140
---
> pve-kernel-2.6.32-46-pve: 2.6.32-175
Click to expand...
So, the only difference is the kernel version, but it appears that -46- is only available in the enterprise subscription. At least, apt-get update doesn't show it in the list.

I've already installed -37- and gonna activate it on next reboot.
 
jazzl0ver said:
So, the only difference is the kernel version, but it appears that -46- is only available in the enterprise subscription. At least, apt-get update doesn't show it in the list.

..
Click to expand...

no, latest kernel is available on all repos. please read the upgrade wiki.

=> ... and configure your repositories.
 
I've read the wiki several times. Can you please check what's wrong here:
root@vm-box-4:/etc/apt# cat sources.list
#deb http://mirror.yandex.ru/debian wheezy main contrib
deb http://http.at.debian.org/debian wheezy main contrib
deb http://download.proxmox.com/debian wheezy pve-no-subscription
deb http://security.debian.org/ wheezy/updates main contrib

root@vm-box-4:/etc/apt# cat sources.list.d/pve-enterprise.list
#deb https://enterprise.proxmox.com/debian wheezy pve-enterprise

root@vm-box-4:/etc/apt# apt-get update
Hit http://download.proxmox.com wheezy Release.gpg
Hit http://download.proxmox.com wheezy Release
Hit http://download.proxmox.com wheezy/pve-no-subscription amd64 Packages
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://security.debian.org wheezy/updates Release
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Get:1 http://http.at.debian.org wheezy Release.gpg [2,373 B]
Hit http://security.debian.org wheezy/updates/main Translation-en
Get:2 http://http.at.debian.org wheezy Release [191 kB]
Ign http://download.proxmox.com wheezy/pve-no-subscription Translation-en_US
Get:3 http://http.at.debian.org wheezy/main amd64 Packages [5,839 kB]
Ign http://download.proxmox.com wheezy/pve-no-subscription Translation-en
Hit http://ceph.com wheezy Release.gpg
Hit http://ceph.com wheezy Release
Hit http://ceph.com wheezy/main amd64 Packages
Ign http://ceph.com wheezy/main Translation-en_US
Ign http://ceph.com wheezy/main Translation-en
Get:4 http://http.at.debian.org wheezy/contrib amd64 Packages [42.0 kB]
Get:5 http://http.at.debian.org wheezy/contrib Translation-en [34.8 kB]
Get:6 http://http.at.debian.org wheezy/main Translation-en [3,846 kB]
Fetched 9,955 kB in 28s (351 kB/s)
Reading package lists... Done

root@vm-box-4:/etc/apt# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@vm-box-4:/etc/apt# dpkg -l | grep pve-kernel
ii pve-firmware 1.1-5 all Binary firmware code for the pve-kernel
ii pve-kernel-2.6.32-33-pve 2.6.32-138 amd64 The Proxmox PVE Kernel Image
ii pve-kernel-2.6.32-34-pve 2.6.32-140 amd64 The Proxmox PVE Kernel Image
ii pve-kernel-2.6.32-37-pve 2.6.32-150 amd64 The Proxmox PVE Kernel Image
Click to expand...
 
your pveversion -v shows:

> proxmox-ve-2.6.32: not correctly installed (running kernel: 2.6.32-37-pve)

try to fix with:

> apt-get update && apt-get install proxmox-ve-2.6.32

latest kernel in the pve-no-subscription repo is 2.6.32-46-pve
 
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