ERROR: column "encrypted" does not exist

[mkarpik79]

Hi Bill,

I'm experiencing below issue with new versions of report. Last one which worked fine was from Apr 19. I'm using Bacula version: 13.0.4 (12 February 2024) x86_64-pc-linux-gnu debian 12.5

Is that related to old DB schema version? What can I do to use your latest report?

/etc/bacula/scripts/baculabackupreport.py -C /etc/bacula/scripts/baculabackupreport.ini --dbname bacula --dbuser bacula --dbpass bacula
- Reading configuration overrides from config file '/etc/bacula/scripts/baculabackupreport.ini', section 'DEFAULT' (if exists), and section 'baculabackupreport'

Problem communicating with database 'bacula' while fetching filtered jobs.

Error on line number: 577
ERROR: column "encrypted" does not exist
LINE 1: ...  PriorJobId, AGE(EndTime, StartTime) AS RunTime, Encrypted ...
                                                             ^

pgcode: 42703

BTW: I appreciate your work very much!

[waa]

Yeah, it seems that the encrypted column first appeared in Bacula Enterprise 16.x (currently 16.0.15), which is tracked by community version 15.x (currently 15.0.2).

At this point, you really only have two choices:

• Upgrade your community version to 15.0.2

• clone the baculabackupreport repository, and then checkout commit 9c456ac2e040b928742f06b72b8de942ac893aaa, which was the last commit before the encrypted feature was added.

Hope this helps!

Bill