suddenly pbs fail - 400 Bad Request : broken pipe

nicolac

Member
Jan 9, 2022
3
0
6
52
after 2 months of regular vm backup (win2019 std ed)
Suddenly PBS fails in backup and the procedure stucked...
What's wrong? how to restart healty VM backup?

thank you in advance

now I have removed this instance from my backup group where I have other vm.
I will put it again when I will know what is happended...

this is the incident PBS log


2022-01-08T22:45:05+01:00: starting new backup on datastore 'storage2': "vm/**/2022-01-08T21:45:02Z"
2022-01-08T22:45:05+01:00: download 'index.json.blob' from previous backup.
2022-01-08T22:45:05+01:00: register chunks in 'drive-scsi0.img.fidx' from previous backup.
2022-01-08T22:45:05+01:00: download 'drive-scsi0.img.fidx' from previous backup.
2022-01-08T22:45:06+01:00: created new fixed index 1 ("vm/**/2022-01-08T21:45:02Z/drive-scsi0.img.fidx")
2022-01-08T22:45:06+01:00: add blob "/mnt/datastore/storage2/vm/**/2022-01-08T21:45:02Z/qemu-server.conf.blob" (414 bytes, comp: 414)
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-01-09T09:41:48+01:00: backup failed: connection error: bytes remaining on stream
2022-01-09T09:41:48+01:00: removing failed backup
2022-01-09T09:41:48+01:00: TASK ERROR: connection error: bytes remaining on stream
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
 
the client/PVE side log might give more info..
 
wich log in /var/log? do you suggest to read?
thnx in advance, or there is something about it in webgui?
 
the corresponding backup task log..
 
this is what I have found, tell me what else you need

2022-01-08T22:45:05+01:00: starting new backup on datastore 'storage2': "vm/100/2022-01-08T21:45:02Z"
2022-01-08T22:45:05+01:00: download 'index.json.blob' from previous backup.
2022-01-08T22:45:05+01:00: register chunks in 'drive-scsi0.img.fidx' from previous backup.
2022-01-08T22:45:05+01:00: download 'drive-scsi0.img.fidx' from previous backup.
2022-01-08T22:45:06+01:00: created new fixed index 1 ("vm/100/2022-01-08T21:45:02Z/drive-scsi0.img.fidx")
2022-01-08T22:45:06+01:00: add blob "/mnt/datastore/storage2/vm/100/2022-01-08T21:45:02Z/qemu-server.conf.blob" (414 bytes, comp: 414)
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-01-09T09:41:48+01:00: backup failed: connection error: bytes remaining on stream
2022-01-09T09:41:48+01:00: removing failed backup
2022-01-09T09:41:48+01:00: TASK ERROR: connection error: bytes remaining on stream
2022-01-09T09:41:48+01:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
 
I meant the PVE task log, not the PBS one.. but that looks like the (network) connection is interrupted