Architecture #23447
closed
Switch back to openssl 1.1 in relayd for now
Added by Alexis Mousset 10 months ago.
Updated 10 months ago.
Description
It seems to cause segfault in relayd on Debian 11, where the system version is 1.1.
[ 289.679974] r2d2-worker-0[20772]: segfault at 1000001b7 ip 00007ff129b62143 sp 00007ff128f49ea0 error 4 in libssl.so.1.1[7ff129b47000+4e000]
We'll update everything at once in the next release.
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/5044
- Status changed from Pending technical review to Pending release
- Target version changed from 1046 to 7.2.11
root@server:~# lddtree /opt/rudder/bin/rudder-relayd
rudder-relayd => /opt/rudder/bin/rudder-relayd (interpreter => /lib64/ld-linux-x86-64.so.2)
libpq.so.5 => /lib/x86_64-linux-gnu/libpq.so.5
libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1
libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1
[...]
This happens because of conflicting versions of openssl used in libpq and embedded in relayd itself.
- Parent task deleted (
#23383)
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.11 and 7.3.7 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by