From 650ac94e6803299a72a068a56be475e540f59f40 Mon Sep 17 00:00:00 2001 From: simon Date: Wed, 17 Aug 2022 18:48:34 +0700 Subject: [PATCH] better wording for es permission error --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 93a6f77..e867e11 100644 --- a/README.md +++ b/README.md @@ -146,12 +146,12 @@ To apply the change permanently depends on your host operating system: - On any other platform look up in the documentation on how to pass kernel parameters. ### Permissions for elasticsearch -If you see a message similar to `AccessDeniedException[/usr/share/elasticsearch/data/nodes]` when initially starting elasticsearch, that means the container is not allowed to write files to the volume. -That's most likely the case when you run `docker-compose` as an unprivileged user. To fix that issue, shutdown the container and on your host machine run: +If you see a message similar to `failed to obtain node locks, tried [/usr/share/elasticsearch/data]` and `maybe these locations are not writable` when initially starting elasticsearch, that probably means the container is not allowed to write files to the volume. +To fix that issue, shutdown the container and on your host machine run: ``` -chown 1000:0 /path/to/mount/point +chown 1000:0 -R /path/to/mount/point ``` -This will match the permissions with the **UID** and **GID** of elasticsearch within the container and should fix the issue. +This will match the permissions with the **UID** and **GID** of elasticsearch process within the container and should fix the issue. ### Disk usage The Elasticsearch index will turn to *read only* if the disk usage of the container goes above 95% until the usage drops below 90% again, you will see error messages like `disk usage exceeded flood-stage watermark`, [link](https://github.com/tubearchivist/tubearchivist#disk-usage).