-
Notifications
You must be signed in to change notification settings - Fork 240
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
munmap_chunk(): invalid pointer, "nuraft_w_0" received signal SIGABRT, Aborted #188
Comments
Hi @kishorekrd Looks like you are using BoringSSL. Do you see the same issue even with OpenSSL? |
Yes, I have seen 3 more different crashes in BoringSSL while running NuRaft. I did not change any NuRaft configuration. I built NuRaft with default configuration. I don't see BoringSSL installed on my system. Here is the list of ssl packages
|
I think it is compiled with a custom library, not from the system path.
What is the CMake message (when you do
If it is not, you may manually add the path
|
Yes, I see it
Even though NuRaft is built with openssl, it is somehow using boringssl. Is there anyway I can force Nuraft to use openssl? |
From what you shared, I think the below is the case
To avoid such wrong linkage, you may need to
|
Thanks for the response. If I don't want to use SSL right now, Can I use mock_ssl by disabling SSL ? |
Yes you can. But does this happen even though you don't set below asio_service::options asio_opt;
asio_opt.enable_ssl_ = true; https://github.com/eBay/NuRaft/blob/master/docs/enabling_ssl.md |
Yes that's correct. I have this following settings asio_service::options asio_opt; What is the default behavior? |
Default is |
Even with false, the issue is happening. I think the main issue is mixing openssl and Boringssl.
|
Hi, Even though I disabled SSL for Nuraft build, I am still seeing asio running some ssl code.
How to disable SSL completely for Nuraft and also asio? How can I build Nuraft with Boringssl? |
@kishorekrd Lines 130 to 139 in 714db11
You can check symbols in
If it is compiled correctly, the only thing you can see should be |
Getting the following crash randomly on Ubuntu 18.04 . Any fix or mitigation ?
The text was updated successfully, but these errors were encountered: