Open eoener-tpgroup opened 7 months ago
Hi, This is strange, could you run the barman diagnose and post the output here, after removing any sensitive information from the output?
Thanks!
Hey, thanks for the fast reply. I upload the output of barman diagnose to this issue. I removed all sensitive information and all other servers, that are configured. I only left one server, which has also the issue (unfortunately multiple servers experience the same issue, not all though). barman_diagnose.txt
After downgrading barman 3.9.0 to 3.6.0 this issue was not present anymore, so I think, this is a issue within the version 3.9.0 (maybe also in 3.10.0)
Hey all,
We are using a passive barman node (barman 3.9.0) to sync created backups and wal files from primary barman node. The retention policy on the primary barman is configured for 3 days and on the passive node for 31 days.
Unfortunately we get following error inside of barman.log
This error occures, when the barman cron starts or when you try to sync the wal files manually
# barman sync-wals XY
Somehow this error also causes, that no new backups from primary database are syncronized to the passive node, at least, thats what I am thinking. Even syncronizing the latest backup to the passive node, doesn't fix the issue with the wals.
Also I tried to understand the sync_wals(self) method inside server.py, but couldn't understand, where it expects 2 arguments. Unfortunately a search with google didn't give any usable result in this case.
Thank you!