Error - Elasticsearch did not come up, check configuration #73
Comments
ifle
changed the title
|
Hi @ifle are you running Please run |
Hi,I have the similar problem,I run the portland-metro sample in Docker. |
|
Hi, @ChingKwanCheung I've never seen the Can you please run |
If the Elasticsearch datadir is not owned by the user specified in $DOCKER_USER, Elasticsearch will fail to start. Since #55 the helper scripts attempt to remedy this situation if the `pelias` script is run as root (which is not recommended but is often done). However, if the `pelias` script is not run as root and the permissions are incorrect, this situation cannot be automatically fixed. command is run to update those permissions. This code attempts to detect that case and recommend the proper command to fix it. Connects #31 Connects #73
If the Elasticsearch datadir is not owned by the user specified in $DOCKER_USER, Elasticsearch will fail to start. Since #55 the helper scripts attempt to remedy this situation if the `pelias` script is run as root (which is not recommended but is often done). However, if the `pelias` script is not run as root and the permissions are incorrect, this situation cannot be automatically fixed. This code attempts to detect that case and recommend the proper command to run (with sudo) and set proper directory permissions. Connects #31 Connects #73
If the Elasticsearch datadir is not owned by the user specified in $DOCKER_USER, Elasticsearch will fail to start. Since #55 the helper scripts attempt to remedy this situation if the `pelias` script is run as root (which is not recommended but is often done). However, if the `pelias` script is not run as root and the permissions are incorrect, this situation cannot be automatically fixed. This code attempts to detect that case and recommend the proper command to run (with sudo) and set proper directory permissions. Connects #31 Connects #73
If the Elasticsearch datadir is not owned by the user specified in $DOCKER_USER, Elasticsearch will fail to start. Since #55 the helper scripts attempt to remedy this situation if the `pelias` script is run as root (which is not recommended but is often done). However, if the `pelias` script is not run as root and the permissions are incorrect, this situation cannot be automatically fixed. This code attempts to detect that case and recommend the proper command to run (with sudo) and set proper directory permissions. Connects #31 Connects #73
Thank you @missinglink for your replying. My docker version is 18.03.0-ce,my operating system is Windows 10 Home Edition.When I run docker ps -a, the output is: |
|
Hi @ChingKwanCheung, Two things to try. First, can you please paste the output of Second can you try the pull request I recently opened, #74? It may offer a suggestion of things to try to fix the issue. |
|
Hi @orangejulius , |
|
Okay @ChingKwanCheung, please try the the branch for #74, it should suggest a command you can run that will fix your issue. |
|
Hi @orangejulius, I have read the page,I couldn't find my problem. I check my datadir in the .env file, it is right.could you tell me which command should I run? |
If the Elasticsearch datadir is not owned by the user specified in $DOCKER_USER, Elasticsearch will fail to start. Since #55 the helper scripts attempt to remedy this situation if the `pelias` script is run as root (which is not recommended but is often done). However, if the `pelias` script is not run as root and the permissions are incorrect, this situation cannot be automatically fixed. This code attempts to detect that case and recommend the proper command to run (with sudo) and set proper directory permissions. Connects #31 Connects #73
If the Elasticsearch datadir is not owned by the user specified in $DOCKER_USER, Elasticsearch will fail to start. Since #55 the helper scripts attempt to remedy this situation if the `pelias` script is run as root (which is not recommended but is often done). However, if the `pelias` script is not run as root and the permissions are incorrect, this situation cannot be automatically fixed. This code attempts to detect that case and recommend the proper command to run (with sudo) and set proper directory permissions. Connects #31 Connects #73
|
Somehow systemd-network took ownership of the e.s. subdir in my data_dir . Changing it back to deploy (1000) didnt help, and I still hit The end of the output of maybe its that 'max vm memory' business, i'll see if i can free up some memory |
|
|
|
from |
|
ok I had added a |
|
This issue seems to have collected a few reports of different problems, so I'm going to close it since I don't think we can make useful progress here. If you are having issues with this docker project then please:
Then if there's still a problem please open a new issue with all the relevant info including which of the above things you tried. Thanks! |
If the Elasticsearch datadir is not owned by the user specified in $DOCKER_USER, Elasticsearch will fail to start. Since #55 the helper scripts attempt to remedy this situation if the `pelias` script is run as root (which is not recommended but is often done). However, if the `pelias` script is not run as root and the permissions are incorrect, this situation cannot be automatically fixed. This code attempts to detect that case and recommend the proper command to run (with sudo) and set proper directory permissions. Connects #31 Connects #73
=) |
|
Hi all, I had the following error at the end of the logs: elasticsearch_1 | ElasticsearchException[failed to bind service]; nested: AccessDeniedException[/usr/share/elasticsearch/data/nodes]; |
I try run the portland-metro sample and have following "Elasticsearch did not come up, check configuration" error. I logged in as 1000 user to Ubuntu. What is wrong? I am new born in linux.
The text was updated successfully, but these errors were encountered: