Fixes back-ported to 5.7 and available with 5.7.4 release.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3635#issuecomment-1905022812
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #3635 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3635#event-11390974707
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) -
Closing now with commits on master—reopen with separate issues for OpenSSL
1.1.1/OpenSSL
Open a separate issue if your config actually manages to init OpenSSL in rank
0(thread#1)—this is the main cause of intermittent crashes. A possible example
would be `db_mysql` with an SSL connection (I'm
> @space88man I just checked it on a test system with exactly one connected
> client, and all 4 TCP listeners as well as the TCP main process show this
> output:
>
> ```
> (gdb) p ossl_err_get_state_int()
> No symbol "ossl_err_get_state_int" in current context.
> (gdb)
> ```
```
# alternatives
@space88man I just checked it on a test system with exactly one connected
client, and all 4 TCP listeners as well as the TCP main process show this
output:
```
(gdb) p ossl_err_get_state_int()
No symbol "ossl_err_get_state_int" in current context.
(gdb)
```
--
Reply to this email directly or
@SipSeb - I think I have a better understanding of the cause for OpenSSL 3
errors now: see #3695.
During your load testing try loading another module in the config that also
uses OpenSSL (e.g. outbound.so). You need not use the functions of this extra
module - just the loading of the module
Just to give a feedback: A nightly build has been running on one of our
affected systems for three weeks now, and we haven't had a crash since. So the
fix seems to improve the behavior. Next step is to test it on a system with
client devices on the other end, handling much more TLS connections
