#36 Barman.cli ERROR: Unhandled exception.

1.x
closed
2014-08-29
2014-02-10
Jason
No

Hello,
I am receiving this error message in our barman backup log file. It does not appear with any regularity but does appear multiply times. I thought it was related to backing up one of our larger servers, which are not completely successfully (I would guess a separate issue). We are using Barman: 1.3.0.

Here is the error message in question:
2014-02-10 11:23:34,275 barman.cli ERROR: Unhandled exception. See log file for more details.
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/barman/cli.py", line 554, in main
p.dispatch(pre_call=global_config, output_file=_output_stream)
File "/usr/lib/python2.6/site-packages/argh/helpers.py", line 47, in dispatch
return dispatch(self, args, kwargs)
File "/usr/lib/python2.6/site-packages/argh/dispatching.py", line 121, in dispatch
for line in lines:
File "/usr/lib/python2.6/site-packages/argh/dispatching.py", line 197, in _execute_command
for line in result:
File "/usr/lib/python2.6/site-packages/argh/dispatching.py", line 153, in _call
result = args.function(args)
File "/usr/lib/python2.6/site-packages/barman/cli.py", line 177, in status
server.status()
File "/usr/lib/python2.6/site-packages/barman/server.py", line 290, in status
self.backup_manager.status()
File "/usr/lib/python2.6/site-packages/barman/backup.py", line 896, in status
self.config.minimum_redundancy))
File "/usr/lib/python2.6/site-packages/barman/output.py", line 231, in result
_dispatch(_writer, 'result', command, *args,
kwargs)
File "/usr/lib/python2.6/site-packages/barman/output.py", line 123, in _dispatch
return handler(
args, **kwargs)
TypeError: result_status() takes exactly 5 arguments (4 given)

I believe this is what you request for people who submit bug reports. The Fully Qualified Doman Name has been censored:
-bash-3.2$ barman status purecastdb01a
Server purecastdb01a:
Description: Purecast DB 01a
PostgreSQL version: 9.2.4
PostgreSQL Data directory: /var/lib/pgsql/9.2/data
PostgreSQL 'archive_command' setting: rsync -a %p
barman@epbackup01.XXXXXXX.XXX:/backup/database/purecastdb01a/incoming/%f
Archive status: last shipped WAL segment 0000000100000184000000F1
Current WAL segment: 0000000100000184000000F2
Retention policies: enforced (mode: auto, retention: RECOVERY WINDOW OF 4 WEEKS, WAL retention: main)
No. of available backups: 0
First available backup: None
Last available backup: None
EXCEPTION: Unhandled exception. See log file for more details.

-bash-3.2$ barman check purecastdb01a
Server purecastdb01a:
ssh: OK
PostgreSQL: OK
archive_mode: OK
archive_command: OK
directories: OK
retention policy settings: OK
compression settings: OK
minimum redundancy requirements: FAILED (have 0 backups, expected at least 1)

-bash-3.2$ barman show-server purecastdb01a
Server purecastdb01a:
conninfo: host=purecastdb01a.XXXXXXXX.XXX user=postgres
ssh_command: ssh postgres@purecastdb01a.XXXXXX.XXX
hba_file: /var/lib/pgsql/9.2/data/pg_hba.conf
retention_policy: RECOVERY WINDOW OF 4 WEEKS
archive_mode: on
config_file: /var/lib/pgsql/9.2/data/postgresql.conf
minimum_redundancy: 1
custom_decompression_filter: None
compression: gzip
retention_policy_mode: auto
archive_command: rsync -a %p barman@epbackup01.XXXXXXX.XXX:/backup/database/purecastdb01a/incoming/%f
basebackups_directory: /backup/database/purecastdb01a/base
data_directory: /var/lib/pgsql/9.2/data
ident_file: /var/lib/pgsql/9.2/data/pg_ident.conf
tablespace_bandwidth_limit: None
lock_file: /backup/database/purecastdb01a/purecastdb01a.lock
current_xlog: 0000000100000184000000F2
description: Purecast DB 01a
bandwidth_limit: None
custom_compression_filter: None
incoming_wals_directory: /backup/database/purecastdb01a/incoming
immediate_checkpoint: False
backup_directory: /backup/database/purecastdb01a
active: True
network_compression: False
post_backup_script: None
wals_directory: /backup/database/purecastdb01a/wals
last_shipped_wal: 0000000100000184000000F1
server_txt_version: 9.2.4
wal_retention_policy: main
pre_backup_script: None

Here is information about the server:
python26-2.6.8-2.el5
Red Hat Enterprise Linux Server release 5.9 (Tikanga)
CPU Name: model name : Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GH
Memory: 4G
Linux epbackup01 2.6.32-300.39.5.el5uek #1 SMP Wed Mar 13 11:26:53 PDT 2013 x86_64 x86_64 x86_64 GNU/Linux
Barman: 1.3.0

All of the dependencies came from you.

Discussion

  • Jason

    Jason - 2014-02-12

    I just figured out how to reproduce this error, just type: "barman status purecastdb01a"

     
    • Dave Rosborough

      Dave Rosborough - 2014-03-19

      I was having the same error. It's dying on the line that should say something like: "Minimum redundancy requirements: satisfied (1/1)"

      If you simply run enough barman backup all's to meet your minimum redundancy requirements, barman status will start working correctly.

       
  • Gabriele Bartolini

    • labels: CLI Barman --> CLI Barman, exception handling
    • status: open --> accepted
    • assigned_to: Giulio Calacoci
     
  • Giulio Calacoci

    Giulio Calacoci - 2014-04-04

    Was a problem related to the output method. we have fixhed this problem and the fix is included in barman 1.3.1.

     
  • Gabriele Bartolini

    • status: accepted --> closed
     
  • Gabriele Bartolini

    Fixed in 1.3.1

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks