So I set this aside for much of 2020 but spent the last week tracking it down. It would appear that this particular error is related to running the backup command from the terminal and using the & to run it in the background. Specifically, the sys.stdout association between the barman backup process and the console/logfile broke because of how I was running the backup. I was attempting to test a backup using a command similar to the following: barman backup pg & running this backup instead from the...
Backup Fails with Large 700 GB Database with no errors