Re: strange error on MyCatalog

Hi Mehrdad,

Am 30.04.2026 um 16:01 schrieb Mehrdad Ravanbod:
> Hi
> 
> I recieved a rather strange error yesterday, on the inbuilt backup job 
> BackupCatalog
> 
> it seems Bacula is saying it does not find the MyCatalog database, and 
> something about a lib-file, but all the other backup jobs are 
> completeing without errors so the database does not seem to have any 
> problems. These lines showd up in the log
> 
>> Bacula2-dir JobId 2862: Error: Runscript: BeforeJob returned non-zero 
>> status=1. ERR=Child exited with code 1
>> Bacula2-dir JobId 2862: BeforeJob: Can't find your catalog (MyCatalog) 
>> in director configuration
>> Bacula2-dir JobId 2862: BeforeJob: /opt/bacula/bin/dbcheck: /usr/ 
>> lib64/libpq.so.5: no version information available (required by /opt/ 
>> bacula/lib/libbaccats-15.0.2.so)
>> Bacula2-dir JobId 2862: shell command: run BeforeJob "/opt/bacula/ 
>> scripts/make_catalog_backup.pl MyCatalog"
> 
> Anyone has seen this beforeor knows what it means??


I have never seen this error.

Underdtanding what it means... well, I think I do -- what it says. The 
binary dbcheck is linked with libbaccats and libbaccats in turn with 
libpq but the shared object file is built without version information. 
What I'm not sure about is if the linker or the running program produces 
the error message, which may be important to understand if this is a 
real software bug, build problem, a packaging issue, a linker / loader 
one, or something else.

Anyway, dbcheck is used in this case to provide information about the 
catalog database to the catalog backup script. It links to the same 
libraries the Dir links to, so it's unexpected that this happens now and 
the Dir runs fine. Have you recently upgraded any software, perhaps 
without restarting the Dir in between?

Also, try running, on the shell,
dbcheck -B -C MyCatalog -c /opt/bacula/etc/bacula-dir.conf
(or whatever paths you use) and
ldd /opt/bacula/bin/dbcheck

We know what we expect from the first call, but let's see. With the 
output of the ldd command in particular you'll be able to see if there 
are other problems with libraries linked to.

If you compare with
ldd /opt/bacula/bin/bacula-dir
we should be seeing similar information, and to check if something was 
upgraded in between, I would recommend comparing time stamps of the 
shared object files affected with start time of the running Dir. The 
latter is shown in bconsole's 'status dir' output, and here, for example
stat /usr/lib/x86_64-linux-gnu/libpq.so.5
shows pretty clearly when the shared object file was created on my 
system -- which is not the same time the file was built for packaging.

If the information you find does not explain things, or a solution is 
not obvious, let's look at it here and we can try to understand things.

Cheers,

Arno




-- 
Arno Lehmann

IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück



_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users