Public bug reported: The pgloader package stopped working after it transitioned to OpenSSL 3. The issue lied in the fact that cl+ssl did not fully support OpenSSL 3. LP: #1960615 fixed the initial issue.
With the above cl+ssl patch applied, when we run pgloader, it invokes the debugger as soon as the first try to dlopen fails for libcrypto.so.1.1. If we tell the debugger to continue, execution resumes normally, with no errors. While swapping the order of libraries to be loaded in cl+ssl would be a workaround for the issue, this seems to be a bug in pgloader and should be fixed there. There is an upstream bug for the issue at https://github.com/dimitri/pgloader/issues/1370 # pgloader --version debugger invoked on a SIMPLE-ERROR in thread #<THREAD "main thread" RUNNING {1000DD4103}>: Error opening shared object "libcrypto.so.1.1": libcrypto.so.1.1: cannot open shared object file: No such file or directory. Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [CONTINUE ] Skip this shared object and continue. 1: [RETRY ] Retry loading this shared object. 2: [CHANGE-PATHNAME] Specify a different pathname to load the shared object from. 3: [ABORT ] Exit from the current thread. (SB-SYS:DLOPEN-OR-LOSE #S(SB-ALIEN::SHARED-OBJECT :PATHNAME #P"libcrypto.so.1.1" :NAMESTRING "libcrypto.so.1.1" :HANDLE NIL :DONT-SAVE NIL)) 0] CONTINUE pgloader version "3.6.3~devel" compiled with SBCL 2.1.11.debian ** Affects: pgloader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968594 Title: Debugger invoked when first cl+ssl shared object is not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgloader/+bug/1968594/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
