Understanding these 'not connected' error messages

[gctwnl]

I've started my first longer run of my combined PVE/PBS system. I made a backup on PVE of my single VM. Then, a few hours later I ran a verification of that backup on the PBS side. While all backups are reported as verified, I see a lot of error messages and seemingly another one in progress of probably failing:



syslog fragment:

Nov 24 23:27:12 pve proxmox-backup-proxy[1103]: starting new backup reader datastore 'pbs-vm-store-1': "/mnt/pbs-backup-1/pbs-vm-store-1"
Nov 24 23:27:12 pve proxmox-backup-proxy[1103]: protocol upgrade done
Nov 24 23:27:12 pve proxmox-backup-proxy[1103]: GET /download
Nov 24 23:27:12 pve proxmox-backup-proxy[1103]: download "/mnt/pbs-backup-1/pbs-vm-store-1/vm/100/2022-11-24T17:59:23Z/index.json.blob"
Nov 24 23:27:12 pve proxmox-backup-proxy[1103]: TASK ERROR: connection error: not connected
Nov 24 23:27:14 pve proxmox-backup-proxy[1103]: starting new backup reader datastore 'pbs-vm-store-1': "/mnt/pbs-backup-1/pbs-vm-store-1"
Nov 24 23:27:14 pve proxmox-backup-proxy[1103]: protocol upgrade done
Nov 24 23:27:14 pve proxmox-backup-proxy[1103]: GET /download
Nov 24 23:27:14 pve proxmox-backup-proxy[1103]: download "/mnt/pbs-backup-1/pbs-vm-store-1/vm/100/2022-11-24T17:59:23Z/index.json.blob"
Nov 24 23:27:14 pve proxmox-backup-proxy[1103]: TASK ERROR: connection error: not connected
Nov 24 23:27:15 pve pvedaemon[1339]: worker exit
Nov 24 23:27:15 pve pvedaemon[1336]: worker 1339 finished
Nov 24 23:27:15 pve pvedaemon[1336]: starting 1 worker(s)
Nov 24 23:27:15 pve pvedaemon[1336]: worker 575966 started
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: starting new backup reader datastore 'pbs-vm-store-1': "/mnt/pbs-backup-1/pbs-vm-store-1"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: protocol upgrade done
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /download
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download "/mnt/pbs-backup-1/pbs-vm-store-1/vm/100/2022-11-24T17:59:23Z/index.json.blob"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/e58d/e58dd635393468ea98dee11773cd49250c51bdfe7b68e21571d42a6bece0b2eb"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/280b/280b3131ab125034299c563aba115c505749693c35cc975511932b193ed402e4"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/243b/243b5d4708c3d37d9b0c29a821eae838f917b9722ca2731660af6024801067f1"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/abdf/abdfd5a5ac1c79b3ceb0326f480f7c1bd486f00a804e20f403694fb95f6085d3"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/4541/4541895a33780b2b1ce892f8f7f3626c44359bae83f45ebb3f3f69d7060d1c0c"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/2548/2548e32e1ce23415bbd6f91fcb8c5d963c4b15ced9899ab9ef5a76c879481865"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/118c/118c13cbbf40b28b87829f5d6564532126796c7a200f5b3a253a3a845fa36ae2"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/985a/985a8f5e825ef78d19841b349646f020cce1799f9cd4b730b55ad7af6d5d7671"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/a709/a70960f1bc89bbb2018e9ca2ea498e349f1c1b70f3bd34e04691e7fb44b8db43"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/1439/1439e4c94e5067675f717cb9ca444fc73c09616bc4a947a4f5975437cb318094"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: GET /chunk
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: download chunk "/mnt/pbs-backup-1/pbs-vm-store-1/.chunks/874d/874dbd4d3e6bd8bbcbe39fb7f10697bdb55bcc5c9525a42611d97858021d3047"
Nov 24 23:27:15 pve proxmox-backup-proxy[1103]: TASK ERROR: connection error: not connected
Nov 24 23:27:21 pve proxmox-backup-proxy[1103]: starting new backup reader datastore 'pbs-vm-store-1': "/mnt/pbs-backup-1/pbs-vm-store-1"
Nov 24 23:27:21 pve proxmox-backup-proxy[1103]: protocol upgrade done
Nov 24 23:27:21 pve proxmox-backup-proxy[1103]: GET /download
Nov 24 23:27:21 pve proxmox-backup-proxy[1103]: download "/mnt/pbs-backup-1/pbs-vm-store-1/vm/100/2022-11-24T17:59:23Z/index.json.blob"
Nov 24 23:27:21 pve proxmox-backup-proxy[1103]: TASK ERROR: connection error: not connected

What may be going on here?

 

[dcsapak]

hi, sorry for the late answer... i can reproduce that but only on a combined pve/pbs system. so far it seems only cosmetic, the client may terminate the connection before the server sees the last response (or some similar issue)
i'll look a bit into it, but it looks like it does not make any issues

 

[dcsapak]

i looked a bit into that, and i can reproduce the issue with the upstream packages we use for our rust server/client. i am not sure if we use it wrong or if there is a bug in those packages, in either case
i opened a bug with them and will see what they say