On Monday, November 18, 2024 6:57:30 PM CET Sobel-Sorenson, Chandler -
(scar) wrote:
> It seems there was a medium security update released for postgresql-13
> on Debian bookworm (oldstable), and right after that bacula stopped
> working due to "no connection to the server". For example, got this
>
> e-mail about the catalog backup:
> > 15-Nov 20:36 hind-dir JobId 0: Fatal error: bdb.h:143 bdb.h:143 query
> > SELECT ClientId,Uname,AutoPrune,FileRetention,JobRetention FROM
> > Client WHERE Name='hind-fd' failed: no connection to the server
> >
> > 15-Nov 20:37 hind-dir JobId 0: Error: sql_create.c:568 Create DB
> > Client record INSERT INTO Client
> > (Name,Uname,AutoPrune,FileRetention,JobRetention) VALUES
> > ('hind-fd','',1,18144000,18144000) failed. ERR=no connection to the
> > server
> >
> > 15-Nov 20:38 hind-dir JobId 0: Fatal error: Could not create Client
> > record. ERR=Query failed: INSERT INTO Log (JobId, Time, LogText)
> > VALUES (0,'2024-11-15 20:37:40','hind-dir JobId 0: Error:
> > sql_create.c:568 Create DB Client record INSERT INTO Client
> > (Name,Uname,AutoPrune,FileRetention,JobRetention) VALUES
> > (''hind-fd'','''',1,18144000,18144000) failed. ERR=no connection to
> > the server
> >
> > '): ERR=no connection to the server
>
> All other jobs are also failing due to similar errors :( Yet, the
>
> server appears to be running normally:
> > ● postgresql@13-main.service - PostgreSQL Cluster 13-main
> > Loaded: loaded (/lib/systemd/system/postgresql@.service;
> > enabled-runtime; vendor preset: enabled)
> > Active: active (running) since Fri 2024-11-15 06:47:24 MST; 3
> > days ago
> > Main PID: 669430 (postgres)
> > Tasks: 7 (limit: 38544)
> > Memory: 18.5M
> > CPU: 4min 3.208s
> > CGroup:
> > /system.slice/system-postgresql.slice/postgresql@13-main.service
> > ├─669430 /usr/lib/postgresql/13/bin/postgres -D
> > /var/lib/postgresql/13/main -c
> > config_file=/etc/postgresql/13/main/postgresql.conf
> > ├─669519 postgres: 13/main: checkpointer
> > ├─669520 postgres: 13/main: background writer
> > ├─669521 postgres: 13/main: walwriter
> > ├─669522 postgres: 13/main: autovacuum launcher
> > ├─669523 postgres: 13/main: stats collector
> > └─669524 postgres: 13/main: logical replication launcher
> >
> > Nov 15 06:47:22 hind systemd[1]: Starting PostgreSQL Cluster
> > 13-main...
> > Nov 15 06:47:24 hind systemd[1]: Started PostgreSQL Cluster 13-main.
>
> What do?
Hello,
I would start with the usual debugging procedures.
For example, check the availability of the server resources such as
disk space used by the postgres service.
After that, check the logs of the Postgres service and perform the
restart of the postgres service while still monitoring the logs.
If everything seems ok, check the database connection parameters
in the bacula-dir configuration.
Use those parameters to connect to the postgres database using
psql tool and check the tables in the database used by Bacula to
confirm that everything is there.
If everything looks ok, you might consider restarting bacula-dir which
might not be necessary. Start another job and it should finish without
database related issues.
Somewhere along this process, you might get a clue about the source
of the problem.
Regards!
--
Josip Deanovic
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
