A container always fails to backup to PBS

charleslcso

Member
Oct 1, 2022
31
1
13
PBS 2.4.6 and PVE 7.4.17 are all uptodate.

Out of all the containers, only 1 always fails to backup to PBS. Once a day backup, and it would fail continuously for 9 days, and then it might be successful for 1-2 days, and fails again.

Here is the output from email:

104confluenceFAILED00:10:00command '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/4042906/root//./ /var/tmp/vzdumptmp2775514_104' failed: exit code 11

104confluenceFAILED00:09:57command '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/4042906/root//./ /var/tmp/vzdumptmp4110880_104' failed: exit code 11

Always exit code 11.

What's wrong with this container? How do I fix this?
 
I now have Exit Code 10. From this thread, I need to increase/change the tmp directory in PVE.

Is it safe if I use udev for this purpose?

root@360g9:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 131955408 0 131955408 0% /dev
tmpfs 26398048 2172 26395876 1% /run
/dev/mapper/pve-root 98497780 9048364 84399868 10% /
tmpfs 131990228 43680 131946548 1% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
/dev/fuse 131072 24 131048 1% /etc/pve
tmpfs 26398044 0 26398044 0% /run/user/0
 

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!

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!