Re: Odd postgreSQL error

On Tue, Nov 12, 2024, at 4:13 PM, B. Smith wrote:
> Hi,
> 
> I'm running Bacula in a FreeBSD 13.2 jail under TrueNAS Core. This weekend all my backups proceeded fine, but I noticed that a backup that should have been suspended started up, so I stopped the job.  A few other incremental jobs ran without incident, but then I got an error in a job after those:

side note, time to get that jail update to fix known vulns.

> 
> Fatal error: backup.c:343 [DE0028] Query failed: DECLARE _bac_cursor CURSOR FOR SELECT Path, Filename, FileIndex, JobId, LStat, DeltaSeq, MD5, JobTDate FROM ((SELECT Path.Path, T1.Filename, T1.FileIndex, T1.JobId, LStat, DeltaSeq, MD5, JobTDate FROM ( SELECT DISTINCT ON (Filename, PathId) JobTDate, JobId, FileId, FileIndex, PathId, Filename, LStat, MD5, DeltaSeq FROM (SELECT FileId, JobId, PathId, Filename, FileIndex, LStat, MD5, DeltaSeq FROM File WHERE JobId IN (1561,1633,1642,1750,1759,2001,2010,2019,2028,2037,2046,2055,2064,2073,2082,2091,2100,2109,2118,2127,2136,2145,2182,2191,2200,2209,2218,2227,2236,2245,2254,2263,2272,2281,2340,2471,2517,2755) UNION ALL SELECT File.FileId, File.JobId, PathId, Filename, File.FileIndex, LStat, MD5, DeltaSeq FROM BaseFiles JOIN File USING (FileId) WHERE BaseFiles.JobId IN (1561,1633,1642,1750,1759,2001,2010,2019,2028,2037,2046,2055,2064,2073,2082,2091,2100,2109,2118,2127,2136,2145,2182,2191,2200,2209,2218,2227,2236,2245,2254,2263,2272,2281,2340,2471,2517,2755) ) AS T JOIN Job USING (JobId) ORDER BY Filename, PathId, JobTDate DESC  ) AS T1 JOIN Path ON (Path.PathId = T1.PathId) WHERE FileIndex > 0 )  ) AS U1 ORDER BY JobTDate, FileIndex ASC: ERR=ERROR:  could not load library "/usr/local/lib/postgresql/llvmjit.so": /usr/local/llvm15/lib/libLLVM-15.so: Undefined symbol "_ZNSt3__122__libcpp_verbose_abortEPKcz"
> 
> I shutdown Bacula, restarted the jail, and still had the same issue. I did not initiate any updates or changes to the system between the working and non-working jobs, and no real job (other than BackupCatalog) would run without the error. Before restoring my database from backup, I used postgres to turn off JIT:
> `alter system set jit=off;`

 JIT is not familiar.  Reading https://www.freshports.org/databases/postgresql16-server it is 

LLVM=on: Build with support for JIT-compiling expressions

Looking on my PostgreSQL 16 server, I find:

[22:01 pg03 dvl ~] % locate llvmjit.so
/usr/local/lib/postgresql/llvmjit.so
[22:05 pg03 dvl ~] % pkg which /usr/local/lib/postgresql/llvmjit.so
/usr/local/lib/postgresql/llvmjit.so was installed by package postgresql16-server-16.4

It sounds like something deleted the file from your system and that's how it became upset.

How was PostgreSQL installed there?

> `ALTER SYSTEM`
> 
> Doing this immediately fixed the problem. But I am mystified as to how it suddenly became a problem in the first place. Any suggestions as to why this suddenly popped up, and whether JIT is even important for Bacula performance?

I can't help you there. 

--
  Dan Langille
  [email protected]

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