vzdump errors

  • Thread starter Thread starter amravit
  • Start date Start date
A

amravit

Guest
command '/usr/bin/rsync --stats --numeric-ids --bwlimit=10240 -aH --delete --no-whole-file --inplace /var/lib/vz/images/107 /var/tmp/vzdumptmp2058' failed with exit code 12

Apr 16 05:20:53 ERROR: Backup of VM 107 failed - command '/usr/bin/rsync --stats --numeric-ids --bwlimit=10240 -aH --delete --no-whole-file --inplace /var/lib/vz/images/107 /var/tmp/vzdumptmp2058' failed with exit code 12

please advice
regards
 
12 is "Error in rsync protocol data stream"

is there enough free space (df /var/tmp/)? Any hint in syslog files?
 
i didnt find any thing in syslog
vps:~# df -h /var/tmp/
Filesystem Size Used Avail Use% Mounted on
/dev/pve/root 95G 3.5G 87G 4% /

this weird
 
I have the following problem:

sudo /usr/sbin/vzdump --suspend 004

INFO: Starting new backup job - vzdump --suspend 004
Use of uninitialized value $vmtype in concatenation (.) or string at /usr/sbin/vzdump line 1308.
INFO: Starting Backup of VM 004 ()
Use of uninitialized value $dir in -d at /usr/sbin/vzdump line 763.
Use of uninitialized value $dir in concatenation (.) or string at /usr/sbin/vzdump line 763.
ERROR: Backup of VM 004 failed - directory '' does not exist

Packgae version:
Version: 1.1-2

i tried with package version 1.1-2 and many variation of the cli but it does not work.

Any ideas?
 
I have the following problem:

sudo /usr/sbin/vzdump --suspend 004

INFO: Starting new backup job - vzdump --suspend 004
Use of uninitialized value $vmtype in concatenation (.) or string at /usr/sbin/vzdump line 1308.
INFO: Starting Backup of VM 004 ()
Use of uninitialized value $dir in -d at /usr/sbin/vzdump line 763.
Use of uninitialized value $dir in concatenation (.) or string at /usr/sbin/vzdump line 763.
ERROR: Backup of VM 004 failed - directory '' does not exist

Packgae version:
Version: 1.1-2

i tried with package version 1.1-2 and many variation of the cli but it does not work.

Any ideas?

you cannot use VMID´s below 100 (openvz limitation).
 
The problem is that 4 of my VMs have VEID below 100.
I tested vzdump with a vm that has VEID above 100 and it works great.
So I think it is a limitation in vzdump not in OpenVZ.
(Actually i have VEs working with ID 1-4).

Thanks for the help!
 
The problem is that 4 of my VMs have VEID below 100.
I tested vzdump with a vm that has VEID above 100 and it works great.
So I think it is a limitation in vzdump not in OpenVZ.
(Actually i have VEs working with ID 1-4).

Thanks for the help!

openvz does not recommend to use ID below 100, therefore we follow this guideline.

see man vzctl:

.... Note that CT ID <= 100 are reserved for OpenVZ internal purposes...

In future version we will improve Proxmox VE in a way that you cannot run VM´s below 100.