Ensure LIBFFI_TMPDIR is exported by init script #80794
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change the init.d script that our packages include to explicitly export LIBFFI_TMPDIR if a value is defined. It turned out that if you configured a value in `/etc/sysconfig/elasticsearch`, that value was visible to the `elasticsearch` script but not the Elasticsearch Java process. Explicitly exporting the variable fixes this problem.
pugnascotia
added
>bug
:Delivery/Packaging
|
Pinging @elastic/es-delivery (Team:Delivery) |
|
Failure does not look at all related. @elasticmachine please run elasticsearch-ci/bwc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change the init.d script that our packages include to explicitly export
LIBFFI_TMPDIR if a value is defined. It turned out that if you
configured a value in
/etc/sysconfig/elasticsearch, that value wasvisible to the
elasticsearchscript but not the Elasticsearch Javaprocess. Explicitly exporting the variable fixes this problem.