On Thu, Nov 09, 2023 at 09:46:25AM -0500, Phil Stracchino wrote: > > One presumes you are aware of how old your Director's OpenSSL is? >
Hello Phil, one presumes correctly. :-) However I was under the impression that a modern bacula (13.0.3) would either be able to talk to clients on new Ubuntu releases if using the bacula-fd from bacula's own repos for 22.04 or that "configure" on Ubuntu 20.04 (still in support) would complain loudly about the age of the system-provided ssl library. Anyway, I compiled openssl-3.0.12 from source on the 20.04 director / stored and provided the location to bacula's configure script using the "--with-openssl" directive in order to recompile it using the new libraries / binaries in /server/openssl-3.012 (the chosen installation location for the modern openssl). Sadly, bacula's "configure" failed to pick up the correct location and insisted on using the system-provided binaries and libraries from the old, system-provided ssl installation, so I guess something is not right w/r to bacula's configure option for openssl. I'd be grateful for any hints on how to fix this. I'm aware I'll need to update the bacula server eventually to Ubuntu 22.04 but for now it seems a bit overkill just because it fails to talk to a single client of among 50 others that are still ticking along nicely. All the best, Uwe -- Uwe Schürkamp // email: <uwe.schuerk...@bertelsmann.de> _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
