-
Notifications
You must be signed in to change notification settings - Fork 195
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
TypeError: '<=' not supported between instances of 'str' and 'NoneType' #1026
Comments
Additional information barman backups happen with "barman backup servername --wait" option included on the server which is backuped is currently no bigger traffic |
I don't think we'll be able to help you with so little amount of information. I would at least need the version of Barman. But that might not be enough. Full diagnose would really help (obfuscate any sensible data) |
Barman Version: 3.10.0 Barman by EnterpriseDB (www.enterprisedb.com) |
Maybe it´s a cool feature request to give and Option for an WAITING for WAL Timeout |
I'm leaving this opened as a feature request for the |
Our Barman System gehts sporatically this issue for some backups:
TypeError: '<=' not supported between instances of 'str' and 'NoneType'
2024-10-20 12:01:06,829 [124729] barman.cli ERROR: '<=' not supported between instances of 'str' and 'NoneType'
See log file for more details.
Traceback (most recent call last):
File "/usr/lib/python3.11/site-packages/barman/cli.py", line 2390, in main
args.func(args)
File "/usr/lib/python3.11/site-packages/barman/cli.py", line 543, in backup
server.backup(
File "/usr/lib/python3.11/site-packages/barman/server.py", line 1610, in backup
self.check(strategy)
File "/usr/lib/python3.11/site-packages/barman/server.py", line 609, in check
self.check_wal_validity(check_strategy)
File "/usr/lib/python3.11/site-packages/barman/server.py", line 1208, in check_wal_validity
wal_info = self.get_wal_info(backup_info)
Barman diagnose says:
Means that the end Date is not setted correctly (Setted to NONE) but backup marked as WAITING FOR WALS.
That causes that the barman check is not working correctly anymore and no backups can be taken.
The text was updated successfully, but these errors were encountered: