The barman check command will report OK when you cannot run list-backup and as a result would have difficulty restoring:
$ barman check db018 Server db018: ssh: OK PostgreSQL: OK archive_mode: OK archive_command: OK directories: OK retention policy settings: OK compression settings: OK minimum redundancy requirements: OK (have 4 backups, expected at least 3) $ echo $? 0 $ barman check db018 --nagios BARMAN OK - Ready to serve the Espresso backup $ barman list-backup db018 ERROR: Unhandled exception. See log file for more details.
There appears to be some processing that list-backup performs that the check command does not. This can leave you in a situation where your checks (e.g. via nagios) are not alerting but your backups are failing or are in an inconsistent state.
Thanks,
Damon
This error is related to ticket #27 and due to a WAL archive database corruption
Fixed by https://sourceforge.net/p/pgbarman/code/ci/90352a0c6de8e86bfb55ab71eac090bf757b568e/