CT backup Error - parameter 'encoded-size': value must have a minimum value of 13 (got 12)

tryweb

New Member
Jul 16, 2020
3
0
1
Taiwan
www.ichiayi.com
I backup VMs, everything is perfect. But I got the error messages when I backup CTs. Does anyone have the same situation?

PVE Version Info:
-------------------------------------------------
Proxmox
Virtual Environment 6.2-10
Search
Node 'aac'
Hour (average)
CPU usage 25.81% of 4 CPU(s)
IO delay 3.33%
Load average 1.51,2.47,2.70
RAM usage 80.64% (6.15 GiB of 7.63 GiB)
KSM sharing 76.29 MiB
HD space(root) 4.38% (2.55 GiB of 58.07 GiB)
SWAP usage 4.74% (339.75 MiB of 7.00 GiB)
CPU(s) 4 x Intel(R) Celeron(R) CPU N3450 @ 1.10GHz (1 Socket)
Kernel Version Linux 5.4.44-2-pve #1 SMP PVE 5.4.44-2 (Wed, 01 Jul 2020 16:37:57 +0200)
PVE Manager Version pve-manager/6.2-10/a20769ed
Server View
Logs
()
proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve)
pve-manager: 6.2-10 (running version: 6.2-10/a20769ed)
pve-kernel-5.4: 6.2-4
pve-kernel-helper: 6.2-4
pve-kernel-5.4.44-2-pve: 5.4.44-2
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.1-5
libpve-guest-common-perl: 3.1-1
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-9
pve-cluster: 6.1-8
pve-container: 3.1-11
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-11
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-10
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1

PBS syslog :
-------------------------------------------------
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: register worker
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: FILE: "/var/log/proxmox-backup/tasks/E4/UPID:pbs:00000261:000001E4:00000009:5F1044EE:backup:pvebackup_ct_100:pveuser@pbs:"
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: starting new backup on datastore 'pvebackup': "ct/100/2020-07-16T12:15:41Z"
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: GET /previous: 400 Bad Request: no previous backup
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: add blob "/pbs-zpool/ct/100/2020-07-16T12:15:41Z/pct.conf.blob" (225 bytes, comp: 225)
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: POST /blob: 400 Bad Request: parameter verification errors
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: parameter 'encoded-size': value must have a minimum value of 13 (got 12)
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: backup ended and finish failed: backup ended but finished flag is not set.
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: removing unfinished backup
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: removing backup snapshot "/pbs-zpool/ct/100/2020-07-16T12:15:41Z"
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: TASK ERROR: backup ended but finished flag is not set.
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: Detected stopped UPID UPID:pbs:00000261:000001E4:00000009:5F1044EE:backup:pvebackup_ct_100:pveuser@pbs:
Jul 16 20:15:42 pbs proxmox-backup-proxy[609]: unregister worker
 

alebeta

Member
Mar 20, 2018
41
3
13
30
gonkar.com
I have the same error... it happens just with 1 LXC, the others are doing just great, even tough they have the same config
 

Levitan

New Member
Jul 23, 2020
6
0
1
30
I have the same problem.
PVE is installed on LVM.
Container is (usually) on the LVM storage.
I moved the hard disk to ext4 and ZFS without success.

I always get the following error:
INFO: Error: HTTP Error 400 Bad Request: parameter verification errors
INFO: parameter 'encoded-size': value must have a minimum value of 13 (got 12)

On my VM it is no problem


*Update:

Now i've install 2 new containers to test it and there it is running without any problems.
 
Last edited:

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
6,491
729
133
33
Vienna
it seems that the check does not work currently for empty blobs, eg. an empty fw.conf for the vm, maybe that is the case here?
(you can check the size in /etc/pve/firewall/)
 

ojaksch

Well-Known Member
Oct 11, 2015
162
32
48
Germany/Earth
it seems that the check does not work currently for empty blobs, eg. an empty fw.conf for the vm, maybe that is the case here?
(you can check the size in /etc/pve/firewall/)
Looks like that, but I'm in doubt as in my case none of the ten CT's has firewall enabled. Some are backup'ing ok, some are failing.
 

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
6,491
729
133
33
Vienna
even if you have the firewall disabled, if there is an empty fw config for the container, its backed up
 

ojaksch

Well-Known Member
Oct 11, 2015
162
32
48
Germany/Earth
even if you have the firewall disabled, if there is an empty fw config for the container, its backed up
Okay, got it. My failing CT's are having an empty file /etc/vzdump/pct.fw (and not /etc/pve/firewall as you mentioned). If I remove that file, all CT's that failed before are backup'ing now.
For me all my tests are finished now to my complete satisfaction. This last issue is solved now - at least for me :)
Thanks for the hint and Bravo for this new product!

EDIT: Wrote back the empty file pct.fw and backup is failing again. Then I wrote one character ("#") into this file and backup is working. Seems to be an issue that if /etc/vzdump/pct.fw is present and empty, backup is failing with parameter 'encoded-size': value must have a minimum value of 13 (got 12)
 
Last edited:
  • Like
Reactions: alebeta
Jul 21, 2020
4
1
3
45
it seems that the check does not work currently for empty blobs, eg. an empty fw.conf for the vm, maybe that is the case here?
(you can check the size in /etc/pve/firewall/)
I have not the firewall active and the backup is not running.
The Firewall was never turned on. What else could it be?
 

alebeta

Member
Mar 20, 2018
41
3
13
30
gonkar.com
Okay, got it. My failing CT's are having an empty file /etc/vzdump/pct.fw (and not /etc/pve/firewall as you mentioned). If I remove that file, all CT's that failed before are backup'ing now.
For me all my tests are finished now to my complete satisfaction. This last issue is solved now - at least for me :)
Thanks for the hint and Bravo for this new product!

EDIT: Wrote back the empty file pct.fw and backup is failing again. Then I wrote one character ("#") into this file and backup is working. Seems to be an issue that if /etc/vzdump/pct.fw is present and empty, backup is failing with parameter 'encoded-size': value must have a minimum value of 13 (got 12)


Thanks, it solved my problem too...
 

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 your own in 60 seconds.

Buy now!