[SOLVED] tmpdir setting in vzdump.conf is ignored

[pizza]

I have a Proxmox 6.2 cluster with this settings on each node:

/etc/vzdump.conf:

# vzdump default settings
tmpdir: /var/lib/vz/dump
#tmpdir: DIR
#dumpdir: DIR
#storage: STORAGE_ID
#mode: snapshot|suspend|stop
#bwlimit: KBPS
#ionice: PRI
#lockwait: MINUTES
#stopwait: MINUTES
#size: MB
#stdexcludes: BOOLEAN
#mailto: ADDRESSLIST
#maxfiles: N
#script: FILENAME
#exclude-path: PATHLIST
#pigz: N

When making a LXC backup (snapshot or suspend), the /var/tmp dir is always used and ignores the custom settings? The LXC container is using NFS storage. The backup storage is PBS.

INFO: starting new backup job: vzdump 110 --storage do-pbs --remove 0 --mode suspend --node node3
INFO: Starting Backup of VM 110 (lxc)
INFO: Backup started at 2020-09-29 14:57:07
INFO: status = running
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: CT Name: server
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/14106/root/ to /var/tmp/vzdumptmp12201
ERROR: Backup of VM 110 failed - command 'rsync --stats -h -X -A --numeric-ids -aH --delete --no-whole-file --sparse --one-file-system --relative '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' /proc/14106/root//./ /var/tmp/vzdumptmp12201' failed: interrupted by signal
INFO: Failed at 2020-09-29 14:57:20
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[oguz]

hi,

works here. what does your pveversion -v say?

to see if it's working create log in two ssh sessions, one of them run:
watch 'ls -alh /var/lib/vz/dump | grep vzdumptmp' (change to your tmpdir setting accordingly if you change it)

and while watching run vzdump 110 again to see if a new file pops up during the backup (that's the temporary file)

 

[pizza]

With the latest updates from pve-manager it works now.

 

[oguz]

great!

just curious, do you remember which version you were using before the upgrade?

 

[pizza]

I had the latest updates from a week ago. Today I updated again and the tmpdir worked,

 

[agapitox]

hi,

works here. what does your pveversion -v say?

to see if it's working create log in two ssh sessions, one of them run:
watch 'ls -alh /var/lib/vz/dump | grep vzdumptmp' (change to your tmpdir setting accordingly if you change it)

and while watching run vzdump 110 again to see if a new file pops up during the backup (that's the temporary file)

Hi @oguz,

That's exactly what's happening to me. If I edit /etc/vzdump.conf and modify the tmpdir, it doesn't work.

here is my pveversion -i:

proxmox-ve: 6.2-1 (running kernel: 5.4.55-1-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-5
pve-kernel-helper: 6.2-5
pve-kernel-5.4.55-1-pve: 5.4.55-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-1
libpve-guest-common-perl: 3.1-2
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-10
pve-cluster: 6.1-8
pve-container: 3.1-13
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-2
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-13
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-14
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1

we are having problems with a backup of a vm that occupies more than 100gb and therefore, fills the /dev/mapper/pve-root so I was trying to change the tmpdir, but it ignores us.

What can we do? updating the pve version is a bit complex as it is a datacenter with more than 10 hosts, and it is in production.

Thank you very much

 

[oguz]

That's exactly what's happening to me. If I edit /etc/vzdump.conf and modify the tmpdir, it doesn't work.

can you show the file?

proxmox-ve: 6.2-1 (running kernel: 5.4.55-1-pve) pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)

is old. you should upgrade to 6.3

 

[agapitox]

can you show the file?

Here it goes:

root@pve7:/mnt/pve/raid10_ssd/bck_tmp/vzdumptmp5234# cat /etc/vzdump.conf
# vzdump default settings

tmpdir: /mnt/pve/raid10_ssd/
#dumpdir: DIR
#storage: STORAGE_ID
mode: snapshot
#bwlimit: KBPS
#ionice: PRI
#lockwait: MINUTES
#stopwait: MINUTES
size: 16000
stdexcludes: 1
remove: 1
mailnotification: failure
mailto:
#maxfiles: N
#script: FILENAME
exclude-path: "/var/log/?*/?*"
pigz: 4
root@pve7:/mnt/pve/raid10_ssd/bck_tmp/vzdumptmp5234#

thanks!

 

[oguz]

Here it goes:

root@pve7:/mnt/pve/raid10_ssd/bck_tmp/vzdumptmp5234# cat /etc/vzdump.conf
# vzdump default settings

tmpdir: /mnt/pve/raid10_ssd/
#dumpdir: DIR
#storage: STORAGE_ID
mode: snapshot
#bwlimit: KBPS
#ionice: PRI
#lockwait: MINUTES
#stopwait: MINUTES
size: 16000
stdexcludes: 1
remove: 1
mailnotification: failure
mailto:
#maxfiles: N
#script: FILENAME
exclude-path: "/var/log/?*/?*"
pigz: 4
root@pve7:/mnt/pve/raid10_ssd/bck_tmp/vzdumptmp5234#

thanks!

OP mentioned that after upgrading it started working again. could you try?

 

[agapitox]

OP mentioned that after upgrading it started working again. could you try?

but I have a question: can I have different versions of pve in the same datacenter? I have a lot of hosts.

thanks

 

[oguz]

but I have a question: can I have different versions of pve in the same datacenter? I have a lot of hosts.

thanks

as long as they are all on the same major version they should work together (6.1 and 6.2 and 6.3 can be in the same cluster, but 5.1 cannot)

 

[Pca]

Hello

btw what is the default tmpdir if not specified anywhere (in the cli or in vzdump.conf) ?
the doc or wiki does not mention it.

 

[oguz]

Hello

btw what is the default tmpdir if not specified anywhere (in the cli or in vzdump.conf) ?
the doc or wiki does not mention it.

if tmpdir is not specified then dumpdir is used (and dumpdir is set by default to your backup directory from your storage config file)