Hello Andreas, i started a large backup via pgbouncer. Unfortunately, the backup is failing. Error message: ... bareos-dir JobId 3: Error: Bareos bareos-dir 25.0.4~pre116.b35277fb6 (30Apr26): OS Information: Debian GNU/Linux 13 (trixie) JobId: 3 Job: backup-dsme01-fd.2026-05-19_00.20.22_22 Backup Level: Full (upgraded from Incremental) Client: "dsme01-fd" 25.0.3~pre96.1f53a5305 (26Mar26) Debian GNU/Linux 11 (bullseye),debian FileSet: "LinuxServer" 2026-05-19 00:15:07 Pool: "Full" (From Job FullPool override) Catalog: "MyCatalog" (From Client resource) Storage: "File" (From Job resource) Scheduled time: 19-Mai-2026 00:20:22 Start time: 19-Mai-2026 00:20:24 End time: 19-Mai-2026 00:46:46 Elapsed time: 26 mins 22 secs Priority: 10 Allow Mixed Priority: no FD Files Written: 450,624 SD Files Written: 450,624 FD Bytes Read: 74,269,024,746 (74.26 GB) FD Bytes Written: 74,269,026,018 (74.26 GB) SD Bytes Written: 74,339,587,424 (74.33 GB) Rate: 46946,3 KB/s Software Compression: None VSS: no Encryption: no Accurate: no Volume name(s): Full-0001|Full-0002 Volume Session Id: 3 Volume Session Time: 1779141929 Last Volume Bytes: 15,652,801,800 (15.65 GB) Non-fatal FD errors: 1 SD Errors: 0 FD termination status: OK SD termination status: OK Bareos binary info: Bareos community build (UNSUPPORTED): Get professional support from https://www.bareos.com Job triggered by: User Termination: *** Backup Error ***
38 2026-05-19 00:46:46 bareos-dir JobId 3: Fatal error: cats/sql_create.cc:803 Fill Path table Query failed: INSERT INTO Path (Path) SELECT a.Path FROM ( SELECT DISTINCT Path FROM batch ) AS a WHERE NOT EXISTS ( SELECT Path FROM Path WHERE Path = a.Path ) : ERR=ERROR: relation "batch" does not exist ZEILE 5: FROM batch ^ 37 2026-05-19 00:46:06 bareos-dir JobId 3: Insert of attributes batch table with 450623 entries start 36 2026-05-19 00:46:06 bareos-sd JobId 3: Elapsed time=00:25:35, Transfer rate=48.42 M Bytes/second 35 2026-05-19 00:46:05 bareos-sd JobId 3: Releasing device "FileStorage" (/media/backups/storage). 34 2026-05-19 00:42:22 bareos-sd JobId 3: New volume "Full-0002" mounted on device "FileStorage" (/media/backups/storage) at 19-Mai-2026 00:42. 33 2026-05-19 00:42:22 bareos-sd JobId 3: Ready to append to end of Volume "Full-0002" size=207 32 2026-05-19 00:42:22 bareos-sd JobId 3: Moving to end of data on volume "Full-0002" 31 2026-05-19 00:42:22 bareos-sd JobId 3: Labeled new Volume "Full-0002" on device "FileStorage" (/media/backups/storage). 30 2026-05-19 00:42:21 bareos-dir JobId 3: Created new Volume "Full-0002" in catalog. 29 2026-05-19 00:42:16 bareos-sd JobId 3: End of medium on Volume "Full-0001" Bytes=75,161,778,387 Blocks=71,682 at 19-Mai-2026 00:42. 28 2026-05-19 00:42:16 bareos-sd JobId 3: User defined maximum volume capacity 75,161,927,680 exceeded on device "FileStorage" (/media/backups/storage). 27 2026-05-19 00:20:25 bareos-sd JobId 3: Ready to append to end of Volume "Full-0001" size=16455154014 26 2026-05-19 00:20:25 bareos-sd JobId 3: Moving to end of data on volume "Full-0001" ... What does this error mean? Best regards, Stefan Andreas Rogge schrieb am Mittwoch, 1. April 2026 um 16:01:33 UTC+2: > Hi Stefan, > > the underlying problem is that the way we're using libpq is apparently > not 100% thread-safe when used in conjuction with TLS. Right now we > haven't understood where exactly things break. Maybe it is Bareos' fault > or libpq's or OpenSSL's. Maybe it only happens on with specific versions > of these components. > Sadly, things will work fine for weeks until one of the database > connections fails in really strange ways (i.e. "PGError: lost > synchronization with server" after some strange TLS errors are logged). > This then takes one or more (presumably long-running) backup jobs with > it. In the end, we decided to disable TLS on our end. > > Having said that, you can still have a TLS encrypted connection to your > database server using PgBouncer or something like that. > Also, feel free to create a PR that adds a configuration setting to > allow (or even require) TLS on the database connection. We will happily > accept a change like that. > > Best Regards, > Andreas > > -- > Andreas Rogge [email protected] > Bareos GmbH & Co. KG Phone: +49 221-630693-86 <+49%20221%2063069386> > http://www.bareos.com > > Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 > Komplementär: Bareos Verwaltungs-GmbH > Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz > > -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bareos-users/fcff1b3a-b5a1-4e06-a9bf-a67330da3692n%40googlegroups.com.
