vzdump hanging in terminal window

BitRausch · May 23, 2010

Hi @all,

I encountered the following problem after updating to 2.6.32-2-pve:
When I start a backup in a terminal window it vzdump does not show when it is finished and hangs in terminal window and I have to terminate the session. I am using nfs for storing backups.:

Terminal Output.

Code:

BigOne:~# vzdump --compress --snapshot 105
INFO: starting new backup job: vzdump --compress --snapshot 105
INFO: Starting Backup of VM 105 (qemu)
INFO: running
INFO: status = running
INFO: backup mode: snapshot
INFO: bandwidth limit: 20000 KB/s
INFO:   Logical volume "vzsnap-BigOne-0" created
INFO: creating archive '/mnt/pve_backup/vzdump-qemu-105-2010_05_23-14_03_36.tgz'
INFO: adding '/mnt/temp/vzdumptmp12159/qemu-server.conf' to archive ('qemu-server.conf')
INFO: adding '/mnt/vzsnap0/images/105/vm-105-disk-1.raw' to archive ('vm-disk-virtio0.raw')

... no reaction after that.

But looking at the log file it shows up as finished:

Code:

May 23 14:03:36 INFO: Starting Backup of VM 105 (qemu)
May 23 14:03:36 INFO: running
May 23 14:03:36 INFO: status = running
May 23 14:03:36 INFO: backup mode: snapshot
May 23 14:03:36 INFO: bandwidth limit: 20000 KB/s
May 23 14:03:37 INFO:   Logical volume "vzsnap-BigOne-0" created
May 23 14:03:37 INFO: creating archive '/mnt/pve_backup/vzdump-qemu-105-2010_05$
May 23 14:03:37 INFO: adding '/mnt/temp/vzdumptmp12159/qemu-server.conf' to arc$
May 23 14:03:37 INFO: adding '/mnt/vzsnap0/images/105/vm-105-disk-1.raw' to arc$
May 23 14:27:30 INFO: Total bytes written: 15281335808 (10.17 MiB/s)
May 23 14:27:57 INFO: archive file size: 7.20GB
May 23 14:27:58 INFO:   Logical volume "vzsnap-BigOne-0" successfully removed
May 23 14:27:58 INFO: Finished Backup of VM 105 (00:24:22)

vzdump.conf

Code:

dumpdir: /mnt/pve_backup
tmpdir: /mnt/temp
mode: snapshot
bwlimit: 20000
maxfiles: 52

pveversion -v

Code:

pve-manager: 1.5-9 (pve-manager/1.5/4728)
running kernel: 2.6.32-2-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.24-8-pve: 2.6.24-16
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.32-2-pve: 2.6.32-7
qemu-server: 1.1-14
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
ksm-control-daemon: 1.0-3

Kind regards

dietmar · May 25, 2010

Is it reproducible, or just happened once?

BitRausch · May 25, 2010

Thx Dietmar.

It is reproducible and it does not matter if the VM is stopped or running.

dietmar · May 25, 2010

BitRausch said:
It is reproducible...

how? (I ask because I can't reporoduce it).

What ssh client do you use? Does it happen when you run directly on the console (no ssh involved)?

BitRausch · May 25, 2010

Thx Dietmar.

Let me try to provide you with as much information as I can:

- PVE Server
Running 3 VM's (1xLinux,1xSBS 2008,1x Windows 7 x32 client)

I am accessing the server remotely through Putty 0.60 with SSH.
(Procedure: Open terminal session -> enter vzdump command -> hit enter. Nothing else)

I can run multiple sessions at a time but only the one with vzdump "crashes". So the terminal does not finish nor does it terminate - meaning is not loosing connection - just sits there. The other terminals are still working fine. I am not running any other backup or scheduled backup at that time.

Storage:
I use a Windows Home Server with MS SFU 3.5 as my backup storage.
fstab mount:

Code:

192.168.16.80:/Pve_Backup /mnt/pve_backup nfs rsize=8192,wsize=8192,hard,intr 0 0

Network bandwidth:
Internet 6K DSL

Internal Bandwidth: Gigabit Network

interfaces

Code:

# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth2 inet manual

auto vmbr0
iface vmbr0 inet static
        address  192.168.100.5
        netmask  255.255.255.0
        gateway  192.168.100.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

auto vmbr1
iface vmbr1 inet static
        address  192.168.16.1
        netmask  255.255.255.0
        bridge_ports eth2
        bridge_stp off
        bridge_fd 0

I can not test it at console directly because the server is physically in a different location. (can do that at the end of the week).

Usually it worked with out any problem until I upgraded to the latest version.

Any other information I can provide to you?

Kind regards

BitRausch · May 25, 2010

addition:

My Client Workstation is a Windows 7 x64.

I will run a couple of more tests this evening (maybe something with vzdump.conf?) Will test it without the .conf file. See if I can find out more...

On a site note:
This is how my storage in the GUI shows the WHS Storage space. It is not a problem - just cosmetic (negative numbers).
View attachment 252

dietmar · May 25, 2010

BitRausch said:
Usually it worked with out any problem until I upgraded to the latest version.

What was the previous version?

BitRausch · May 25, 2010

The version before upgrade:

pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-4
pve-kernel-2.6.24-8-pve: 2.6.24-16
pve-kernel-2.6.32-1-pve: 2.6.32-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
ksm-control-daemon: 1.0-3

dietmar · May 26, 2010

BitRausch said:
The version before upgrade:

vzdump: 1.2-5

So it is the same vzdump version - strange.

BitRausch · May 26, 2010

hi dietmar,

after a couple of tests last night the result did not changed. Whenever I start a vzdump manually in a terminal it does not come back. (Changed Port, renamed vzdump.conf and entered the parameters manually, tried a different vm for backup...)
But I tried to reproduce the error on a different server (test server) and I was not able to do that. So I think it is something with my production server but I can not find the culprit. So maybe something went "wrong" when I updated the server.
(Additional information: I started this server with pve 1.4 and gradually updated it to the current version as recommended.)

My question: Is it possible to reinstall the update without actually going through a complete re-installation of the server? Maybe this will fix the problem.

Kind regards

Kind regards

dietmar · May 28, 2010

BitRausch said:
My question: Is it possible to reinstall the update without actually going through a complete re-installation of the server? Maybe this will fix the problem.

Simply download the debian files, and install them with "dpkg -i xzy.deb" - but i doubt that this solves any problem.

spdriver · May 28, 2010

Hi BitRausch,

you can use "strace" in your terminal/ssh window to get an insight what the "vzdump" is actually doing (or not doing)

"Using strace to debug application errors"
at http://www.debian-administration.org/articles/352

There are some "strace" like perl modules, just for debugging perl scripts only.
http://search.cpan.org/~darnold/Devel-STrace-0.31/lib/Devel/STrace.pod

kind regards

BitRausch · May 28, 2010

Thank you spdriver!!

I will check it out this weekend and report back.

kind regards

Search

Search

vzdump hanging in terminal window

BitRausch

Renowned Member

dietmar

Proxmox Staff Member

BitRausch

Renowned Member

dietmar

Proxmox Staff Member

BitRausch

Renowned Member

BitRausch

Renowned Member

dietmar

Proxmox Staff Member

BitRausch

Renowned Member

dietmar

Proxmox Staff Member

BitRausch

Renowned Member

dietmar

Proxmox Staff Member

spdriver

New Member

BitRausch

Renowned Member