-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible with pgbarman 1.6.0? #11
Comments
Thanks for your report! We're still on barman 1.3.x in production and I've never tested with barman 1.6, so it's quite likely that rbarman/check-barman is incompatible. I'll try to investigate the next couple of days |
Hi, I'm on centOS 6.5 and I found where to change the test in folder /usr/local/rvm/gems/ruby-2.1.3/gems/rbarman-0.0.15/lib/rbarman , you need to edit the file cli_command.rb : change : to
|
Thanks, I'll have a look. Should be easy to solve |
Greetings dev.
Recently updated our pgbarman installation to 1.6.0 and decided it was time to have some proper checks to verify the backups are proper.
However I am having some issues when running most of the check-barman actions. The psql setup is master --> slave replication with wal_level hot standby. Barman is running on the slave host, dumping to a locally mounted share.
whoami
barman
gem list rbarman
*** LOCAL GEMS ***
rbarman (0.0.15)
barman -v
1.6.0
The only check that works
The checks that fails
Although SSH works according to barman itself
The ssh check I can live without. However the "good" checks spits out more fails which I interpret as being related to rbarman:
./check-barman.rb -a last_wal_received -s main -w 300 -c 600
./check-barman.rb -a failed_backups -s main -w 1 -c 2
barman show-backup main latest
Any help towards a solution would be appreciated.
The text was updated successfully, but these errors were encountered: