Did you upgrade any other software on the Director or PostgreSQL servers at
the same time?
Did you edit this output? Two things seem strange to me:
1) The "Could not open Catalog" error has database "bacula" but the "Unable to
connect" error has Database=baculadb.
2) The user name in the Postgr
Hi all,
I recently upgraded my Bacula Director from version 9.x to 13.0.4 on a
Debian 12 system. I successfully ran the update_postgresql_tables script
against the PostgreSQL catalog, and Bacula Director started up without any
issues.
However, after starting a few backup jobs (typically around 8
