This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
Evaluate (and maybe implement) JNA workaround #74
Assignees
Labels
bug
Something isn't working
Comments
|
Confirmend. When manually implementing the change it allowed Elasticsearch to start. |
|
Make sure to use the directory from #72 and not an arbitraty one. |
|
Please make sure to activate this change in all tests as well. Maybe it can help to solve our ongoing problem with tests in Molecule. |
|
On a testing system Elasticsearch starts without any problem. Seems like this problem appeared due to unknown hardening measures on the system. |
widhalmt
added a commit
that referenced
this issue
Sep 20, 2022
fixes #74 Basically just move the `tmp` directory of Elasticsearch to a directory we're sure is writable for Elasticsearch
Merged
widhalmt
added a commit
that referenced
this issue
Dec 16, 2022
* Implement JNA workaround fixes #74 Basically just move the `tmp` directory of Elasticsearch to a directory we're sure is writable for Elasticsearch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I stumbled about an error in an Elasticsearch installation on Ubuntu 20.04 LTS. It seems that
/tmpis built there in a way that doesn't work with newer versions of Elasticsearch.This may or may not be related to https://stackoverflow.com/questions/47824643/unable-to-load-jna-native-support-library-elasticsearch-6-x/50371992#50371992 . Please test if you can get Elasticsearch to run on this system without the workaround or with it. If you need it, implement the steps from the thread as optional (with default off)
The text was updated successfully, but these errors were encountered: