-
Notifications
You must be signed in to change notification settings - Fork 647
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
Witness_node crash when starting ElasticSearch plugin #2490
Milestone
Comments
I am unable to stably reproduce this issue. |
abitmore
modified the milestones:
Future Feature Release,
6.0.0 - Protocol Upgrade Release
Jul 25, 2021
Fixed by #2495. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
It's caused by a bug incurl
: curl/curl#3548Update: that bug was fixed in curl 7.68.0-1ubuntu2.6 , actually our issue is different.
Update:
GET
.POST
sent before we sending theGET
(see ElasticSearch plugin startup check is incomplete #2494).CURLOPT_HTTPGET
indoCurl()
forGET
, so it may be actually sending aPOST
, solibcurl
may try to accessCURLOPT_POSTFIELDS
.CURLOPT_POSTFIELDS
indoCurl()
forGET
, which is a pointer and was pointing to a temporary variable which had been destructed already, the memory address may or may not be accessible. Anyway, accessing it is wrong.Host Environment
Please provide details about the host environment. Much of this information can be found running:
witness_node --version
.Additional Context
The crash started to happen when I upgraded my server with
sudo apt upgrade
to upgrade ElasticSearch to7.13.4
, at the same time kernel and some other packages got upgraded too. After the upgrade, before a reboot,witness_node
worked fine. After reboot,witness_node
starts to crash.The pre-built
witness_node
binary (with different versions of libraries statically linked) crashes too. So perhaps the issue is triggered by some changes in kernel.The text was updated successfully, but these errors were encountered: