vzdump times out no clue why

hmontoliu

Renowned Member
Jun 9, 2014
7
0
66
Hello

since a few weeks ago the vzdump process times out.

Here is the log:

Code:
vzdump 100 --quiet 1 --mailto root@localhost --mode snapshot --compress lzo --storage backups-VMs --node node01host

100: jun 07 02:00:04 INFO: Starting Backup of VM 100 (qemu)
100: jun 07 02:00:04 INFO: status = running
100: jun 07 02:00:05 INFO: backup mode: snapshot
100: jun 07 02:00:05 INFO: ionice priority: 7
100: jun 07 02:00:05 INFO: creating archive '/var/local/backups-VMs/dump/vzdump-qemu-100-2014_06_07-02_00_04.vma.lzo'
100: [COLOR=red]jun 07 02:00:08 ERROR: got timeout
[/COLOR]100: jun 07 02:00:08 INFO: aborting backup job
100: [COLOR=red]jun 07 02:00:12 ERROR: Backup of VM 100 failed - got timeout


[/COLOR]

The destination is a mounted ext3 partition:

Code:
/dev/mapper/backup-VMs on /var/local/backups-VMs type ext3 (rw)

There is plenty of free space to allocate the whole backup:

Code:
/dev/mapper/backup-VMs
                      459G  199M  435G   1% /var/local/backups-VMs


Monitor shows the following status:

Code:
qm> info backup
Backup status: error - backup cancelled
Backup file: /dev/fdname/backup
Backup uuid: 08361a8c-2048-4223-98d5-59cea2d713a8
Total size: 268435456000
Transferred bytes: 65536 (0%)
Zero bytes: 61440 (0%)


The configuration of that VM is:

Code:
boot: cdn
bootdisk: virtio0
cores: 4
cpu: host
ide2: local:iso/virtio-win-0.1-65.iso,media=cdrom,size=60558K
memory: 3056
name: Server01
net0: rtl8139=8A:59:2D:39:AC:48,bridge=vmbr0
net1: e1000=7A:04:2D:4D:56:A6,bridge=vmbr0
net2: virtio=D6:3F:07:4E:EA:C1,bridge=vmbr0
onboot: 1
ostype: w2k8
sockets: 1
virtio0: localvms:100/vm-100-disk-1.qcow2,size=250G

The versions I'm running are:

Code:
:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1



I have no clue of what is happening so any help would be appreciated.

Thanks in advance
 
You should first update your installation, because you run a quite old version.

Sure I should, but it is a production server and I can't schedule a upgrade for a while.

I've found this thread:

http://forum.proxmox.com/threads/18617-vzdump-timeout

I'll tell you if increasing the timeout value allows vzdump to continue and start the backup or not:

Code:
--- /usr/share/perl5/PVE/QMPClient.pm.bak       2014-06-16 08:47:43.000000000 +0200
+++ /usr/share/perl5/PVE/QMPClient.pm   2014-06-16 08:48:43.000000000 +0200
@@ -89,7 +89,7 @@
                 $cmd->{execute} eq 'snapshot-drive'  ) {
            $timeout = 10*60; # 10 mins ?
        } else {
-           $timeout = 3; # default
+           $timeout = 120; # test
        }
     }