-
Hello, I'm building xmlsec 1.3.7 on Rocky Linux 8.9, using gcc 12, with openssl 3.0.15, libxml2 2.12.10, libxslt 1.1.43 and gcrypt 1.11.2 I tried to run one blocking test manually:
I get this output:
but then, the process is stuck, it doesn't exit. I must hit Ctrl-C to abort. Is this an already known issue? |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments
-
Something is not right with openssl. Not sure if RockyLinux does any openssl patches but this test can't fail with "certificate has expired" error because the specific (valid) verification time is passed to the test in the command line: "--verification-gmt-time 2022-12-20+00:00:00" I would recommend to try and build xmlsec against custom built openssl downloaded from openssl.org website. Re hangs, I would recommend to attach debugger to the hanging process and then see what is going on. Again, it smells like something is hanging during shutdown / cleanup and openssl is the most likely option. |
Beta Was this translation helpful? Give feedback.
-
Sorry for delay, I got RockyLinux installed and I can't reproduce the issue using the latest versions of all packages. Please consider upgrading to the latest versions:
|
Beta Was this translation helpful? Give feedback.
-
Thanks a lot for the time you took to perform those tests!
I will perform more tests, upgrading OpenSSL and libxml2, and see how it goes. Thanks again! |
Beta Was this translation helpful? Give feedback.
-
I switched to older versions of OpenSSL (3.0.17) and LibXML2 (2.12.10) using same configure/ build commands as above:
And results are the same --> all tests pass and there are no hangs. So I would personally try the following: |
Beta Was this translation helpful? Give feedback.
-
Thanks again for making more tests. On my side I switched to the "master" version of xmlsec and libxml2 2.14.5 and the tests are currently running with no hangs (the tests take a long time, but it's on a virtual machine and we do have lots of performance issues). In any case it looks like my problem is not with the libxml2 version. I'll have to rebuild xmlsec 1.3.7 as I'm starting to think something went wrong during the build as you haven't found any issue on your side... And there's no reason this problem would go unnoticed. Especially since we see both unexpected errors reported by the tests, and hangs. That's a lot. Regarding the stack trace when the process is stuck, I took one using gdb, unfortunately this in not built in debug mode so it's not very informative:
|
Beta Was this translation helpful? Give feedback.
-
Make sure you are building LibXSLT and XMLSec against correct version of LibXML2 and that the same version is loaded at runtime. |
Beta Was this translation helpful? Give feedback.
-
Hello, I've rebuilt xmlsec 1.3.7 from scratch and now the tests are OK (well they are still running, but they don't get stuck). I must have made a mistake when building the first time, probably a library version mismatch as you suggested... I'm very sorry for wasting your time, please accept my apologies and I can't thank you enough for looking into this issue. |
Beta Was this translation helpful? Give feedback.
-
Sorry for the delay. It turns out tests failed on both version 1.2.42 and 1.3.7. They lasted looong (slow virtual machine), so I first thought they were OK. The next step for me will be to restart from scratch, rebuilding the dependencies (ssl libxml2...) with the same versions as you. Meanwhile we continue to use the old version, it's no big deal. |
Beta Was this translation helpful? Give feedback.
Sorry for delay, I got RockyLinux installed and I can't reproduce the issue using the latest versions of all packages. Please consider upgrading to the latest versions: