Backup with backup client failed - error reading a body from connection

[movsiv]

Hello,

I try to backup data with the proxmox backup client.

Technical data:
- pbs: V. 2.2.3
- client: Linux Debian with proxmox backup client V. 2.2.1

At the beginning, everything works fine. But since maybe 2 hours oder 4 hours, the backup failed.

I add "--verbose" to the client and
- on client side the log output suddenly stops. At last try there was "http/2.0 connection failed" as last log entry. But not everytime.
- on server side these were the last entries:

2022-06-26T10:57:03+02:00: upload_chunk done: 1125480 bytes, d6dfffffafa7b05e0839744354203e193a307dd07385bddcd0dc7484043513a4
2022-06-26T10:57:03+02:00: upload_chunk done: 3771678 bytes, c799c11acab8434f08633fcf86b3a5feb729fd2665b09a409c98549885550b69
2022-06-26T10:57:03+02:00: upload_chunk done: 1325019 bytes, 7cd4ab6d559b8b1d567a4f5f7c0b980bd9e4f89258c8600e37d5fe7f3b3f5a48
2022-06-26T10:57:03+02:00: upload_chunk done: 4377663 bytes, 8f7e0b20dd9c1d0b7b692f04f8ccb3da1d42444c480c68e02547cce044cec5f2
2022-06-26T10:57:04+02:00: upload_chunk done: 3862137 bytes, 600339ee9789ec4a26bc2d26d504ec2853b0057dc3e6a9d9724ddf47d4bf103d
2022-06-26T10:57:04+02:00: POST /dynamic_chunk
2022-06-26T10:57:04+02:00: upload_chunk done: 4380241 bytes, 73c6e511787f40a9feb9f09921751a716a8b94455c14dc6eb6430bae6b7b514b
2022-06-26T11:00:24+02:00: POST /dynamic_chunk: 400 Bad Request: error reading a body from connection: connection reset
2022-06-26T11:00:24+02:00: backup failed: connection error: connection reset
2022-06-26T11:00:24+02:00: removing failed backup
2022-06-26T11:00:24+02:00: POST /dynamic_chunk: 400 Bad Request: error reading a body from connection: connection reset
2022-06-26T11:00:24+02:00: TASK ERROR: connection error: connection reset

I had to backup over 300 GB of data.

Is there the possibility to restart/resume backup and do not start from the beginning?
Or is there another switch to have more details on the log why it fails?


thanks for helping

Alex

 

[SpinningRust]

Hi, I'm facing the same issue out of the blue.
My data backup runs every week and the pool is roughly 30Tb big, usual backup size is around 900Gb. Since this week, the backups for this particular job fails with:

HTTP/2.0 connection failed
catalog upload error - channel closed
Error: pipelined request failed: connection reset

Did you ever fix this?
Or does anyone have an idea? my system details are below the spoiler

Spoiler: sytem details

PVE:
proxmox-ve: 8.1.0 (running kernel: 6.5.13-1-pve)
pve-manager: 8.1.10 (running version: 8.1.10/4b06efb5db453f29)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5.13-3-pve-signed: 6.5.13-3
proxmox-kernel-6.5: 6.5.13-3
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2.16-15-pve: 6.2.16-15
proxmox-kernel-6.2.16-14-pve: 6.2.16-14
proxmox-kernel-6.2.16-10-pve: 6.2.16-10
proxmox-kernel-6.2.16-8-pve: 6.2.16-8
proxmox-kernel-6.2.16-6-pve: 6.2.16-7
pve-kernel-6.2.16-5-pve: 6.2.16-6
pve-kernel-6.2.16-4-pve: 6.2.16-5
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.3
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.5
libpve-cluster-perl: 8.0.5
libpve-common-perl: 8.1.1
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.6
libpve-network-perl: 0.9.6
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.1.4
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.5-1
proxmox-backup-file-restore: 3.1.5-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.5
pve-cluster: 8.0.5
pve-container: 5.0.9
pve-docs: 8.1.5
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.10-1
pve-ha-manager: 4.0.3
pve-i18n: 3.2.1
pve-qemu-kvm: 8.1.5-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.1.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve1

PBS:
proxmox-backup: not correctly installed (running kernel: 6.5.11-8-pve)
proxmox-backup-server: 3.1.5-1 (running version: 3.1.5)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-6-pve-signed: 6.5.11-6
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2.16-14-pve: 6.2.16-14
proxmox-kernel-6.2.16-8-pve: 6.2.16-8
proxmox-kernel-6.2.16-6-pve: 6.2.16-7
pve-kernel-6.2.16-4-pve: 6.2.16-5
pve-kernel-5.15.108-1-pve: 5.15.108-1
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.128-1-pve: 5.4.128-2
pve-kernel-5.4.106-1-pve: 5.4.106-1
ifupdown2: 3.2.0-1+pmx8
libjs-extjs: 7.0.0-4
proxmox-backup-docs: 3.1.5-1
proxmox-backup-client: 3.1.5-1
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.5
proxmox-widget-toolkit: 4.1.5
pve-xtermjs: 5.3.0-3
smartmontools: 7.3-pve1
zfsutils-linux: 2.2.3-pve2