Skip to content
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

WAL history file cannot be parsed and is causing an error #10

Open
speze88 opened this issue Feb 23, 2016 · 0 comments
Open

WAL history file cannot be parsed and is causing an error #10

speze88 opened this issue Feb 23, 2016 · 0 comments

Comments

@speze88
Copy link

speze88 commented Feb 23, 2016

Hi,

I've encountered an error with check-barman for the actions last_wal and mssing_wal, that is caused by a WAL history file. The history file is created when the timeline changes. In my case this always occurs after performing a failover in a master/slave cluster managed by crm.

./check-barman.rb -a last_wal -s mypgcluster -w 5 -c 10

The check command is causing the following error:

/var/lib/gems/1.9.1/gems/rbarman-0.0.15/lib/rbarman/wal_file.rb:109:in parse': name has to be exactly 24 chars (RBarman::InvalidWalFileNameError) from /var/lib/gems/1.9.1/gems/rbarman-0.0.15/lib/rbarman/cli_command.rb:196:inblock in parse_wal_files_list'
from /var/lib/gems/1.9.1/gems/rbarman-0.0.15/lib/rbarman/cli_command.rb:194:in each' from /var/lib/gems/1.9.1/gems/rbarman-0.0.15/lib/rbarman/cli_command.rb:194:inparse_wal_files_list'
from /var/lib/gems/1.9.1/gems/rbarman-0.0.15/lib/rbarman/cli_command.rb:119:in wal_files' from /var/lib/gems/1.9.1/gems/rbarman-0.0.15/lib/rbarman/cli_command.rb:71:inblock in backups'
from /var/lib/gems/1.9.1/gems/rbarman-0.0.15/lib/rbarman/cli_command.rb:68:in each' from /var/lib/gems/1.9.1/gems/rbarman-0.0.15/lib/rbarman/cli_command.rb:68:inbackups'
from /var/lib/gems/1.9.1/gems/rbarman-0.0.15/lib/rbarman/cli_command.rb:54:in backup' from /var/lib/gems/1.9.1/gems/rbarman-0.0.15/lib/rbarman/backup.rb:298:inby_id'
from ./check-barman.rb:84:in check_last_wal_received' from ./check-barman.rb:237:in

'

The error disappears if the 00000005.history is deleted and xlog rebuilded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant