-
Notifications
You must be signed in to change notification settings - Fork 580
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Return of OpenSSL's libcrypto's deadlock #3455
Labels
Comments
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days. |
Can anyone try to look at the problem ? |
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OpenSIPS version you are running
Describe the bug
As its name indicates, I happen to have a problem of deadlocks with some OpenSSL's libcrypto's mutex acquisition calls.
To Reproduce
I am not able to reproduce this bug, it heavily depends on the load for the servers and the concurrent calls from multiple processes to functions using libcrypto.
Expected behavior
Not having a deadlock 😅
Relevant System Logs
You will see below a full stack trace (that I got with opensips-cli) that showcases the deadlock. You can also see that there are several calls to "get_static_lock" that seem to be part of the problem but it is not, I was trying to mitigate (or completely suppress) the risk of a deadlock by locking the different parts of my opensips' script that were calling methods using libcrypto (but it would be better to try to fix the root cause of the problem).
I had to anonymize the sensitive data inside the stacktrace but none of these data is relevant for my issue.
gdb_opensips_20240828_094216.txt
OS/environment information
Feel free to ask for any additional information.
The text was updated successfully, but these errors were encountered: