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 PostgreSQL server log is just "" (i.e. empty): DETAIL: pool_passwd file does not contain an entry for "" <<<<<<<<< __Martin >>>>> On Fri, 18 Jul 2025 22:25:22 +0200, Saiful Bhuiyan said: > > 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 to 10), the > Director seems to hang. Once this happens, I am unable to restart the > bacula-director service unless I reboot the server. After a reboot, it > works again briefly for a few jobs before failing in the same way. > > Logs from the Bacula Director server (journalctl): > > Jul 18 21:39:38 "http://HOSTNAME.DOMAIN.com"HOSTNAME.DOMAIN.com systemd[1]: > Starting bacula-director.service - Bacula Director Daemon service... > Jul 18 21:40:08 "http://HOSTNAME.DOMAIN.com"HOSTNAME.DOMAIN.com > bacula-dir[2131]: bacula-dir: dird.c:1462-0 Could not open Catalog > "MyBackupCatalog", database "bacula". > Jul 18 21:40:08 "http://HOSTNAME.DOMAIN.com"HOSTNAME.DOMAIN.com > bacula-dir[2131]: bacula-dir: dird.c:1468-0 postgresql.c:336 Unable to > connect to PostgreSQL server. Database=baculadb User=baculatest > Jul 18 21:40:08 "http://HOSTNAME.DOMAIN.com"HOSTNAME.DOMAIN.com > bacula-dir[2131]: Possible causes: SQL server not running; password > incorrect; max_connections exceeded. > Jul 18 21:40:08 "http://HOSTNAME.DOMAIN.com"HOSTNAME.DOMAIN.com > bacula-dir[2131]: 18-Jul 21:40 bacula-dir ERROR TERMINATION > > > Logs from the PostgreSQL server (journalctl log): > > FATAL: SCRAM authentication failed > DETAIL: pool_passwd file does not contain an entry for "" > > > > Despite this, I can connect manually from the Bacula Director server to the > PostgreSQL database using psql with the baculatest user and password. > > > My pool_hba.conf on the Pgpool host includes: > > host all all 10.10.0.0/12 scram-sha-256 > > > And the pool_passwd file contains: > > baculatest:<encrypted password string starting with 'AES'> > > > What could be causing Bacula Director to lose access to the PostgreSQL > catalog after running several jobs, even though manual connections from the > same host succeed? Could it be an issue with Pgpool authentication, > connection limits, or something else? > > Any insights would be greatly appreciated. > > Thanks! > _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
