On Fri, Apr 29, 2022 at 04:08:31PM +0200, Georg Pfuetzenreuter wrote:
Hi Axel,
Sorry, scrap my previous email. I realized too late you only encounter this issue with the HTTPS listener, not the plain HTTP one.
It seems the Orthanc code throws this exception in an else clause, so possibly it's not always an accurate error message: if (isSslError) { throw OrthancException(ErrorCode_SslInitialization); } else { throw OrthancException(ErrorCode_HttpPortInUse, " (port = " + boost::lexical_cast<std::string>(port_) + ")"); } }
Running Orthanc with HTTPS enabled through strace seems to make it stutter with libcrypto:
openat(AT_FDCWD, "/lib64/libcrypto.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib64/libcrypto.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) munmap(0x7fb5940ea000, 24027) = 0 write(2, "E0429 15:38:53.847614 OrthancExc"..., 47) = 47 write(2, "The TCP port of the HTTP server "..., 63) = 63
Manually linking either of our available libcrypto libraries makes it continue, but eventually segfaults in an OpenSSL FIPS Self Check.
I think this is an issue with the libraries the package is build against - but I'm not too sure.
Originally I wanted to suggest raising an issue with the packager - but now I realize you are the packager! :-)
I'm not sure if any of the above is helpful, but possibly you could try checking if it needs any specific setup of libcrypto/openssl and compare it to the libraries installed on Debian?
It should not open libcrypto.so usually, but libcrypto.so.<major> Install libopenssl-devel to see if that makes it work (as that contains libcrypto.so) Ciao, Marcus