I've looked at similar situations, apparently this can be caused by
multi-threaded programming, accessing the socket on different threads at the
same time. The solution is to make sure you're not writing to it on one thread
and closing it on another but I'm at a loss as to how to check this in K
We've been testing this further.
- The problem doesn't occur when using TCP\UDP with-out making changes to our
existing configuration.
- If we change 'children' from 16 to 1 then the problem no longer occurs when
using TLS.
Are there any significant drawbacks setting 'children' to 1? Thus far
Is libcrypto using threads and deals with sockets itself from point of view of
closing them? Kamailio is multi-process and at a given moment, only one process
is supposed to write to the socket. Moreover, afaik, writing to a closed socket
is not causing SIGSEGV.
>From the log messages, it seems
We tried changing children to 8 and the problem still occurs, 1 is the only
safe value thus far.
Not sure exactly on the relationship between Kamailio and Libcrypto, does
Kamailio need to interact with Libcrypto in a specific order? For example, if
there are multiple messages sent to Kamailio b
About the question "Are there any significant drawbacks setting 'children' to
1? Thus far everything appears to be working as expected."
You will not get a good performance this way, as Kamailio can't process any new
messages if there is e.g. a database operation running in the one child. You
wi
Have you got the chance to install the debug symbols for libssl and libcrypto?
Will allow to track inside those libraries where the crash happened and see if
it is related to kamailio in some way.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
Not yet, I took a quick look at the process but will have to come back to it at
some point later this week when I have more time. We currently have limited use
of Kamailio in our production environment pending resolution of this issue.
--
You are receiving this because you are subscribed to thi
We've installed the latest debug symbols for libssl and libcrypto compiled from
here:
https://www.openssl.org/source/openssl-1.1.1b.tar.gz
We've also updated Kamailio to 5.2.1.
Unfortunately the problem remains the same, see above for the updated core dump.
Please let me know if there's anythin
