Skip to content
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

default.data.path tried although data.path defined #26883

Closed
andreas-p opened this issue Oct 4, 2017 · 3 comments
Closed

default.data.path tried although data.path defined #26883

andreas-p opened this issue Oct 4, 2017 · 3 comments

Comments

@andreas-p
Copy link

With 5.6.2 on Debian9, I configured data.path to point to a dedicated partition.
When starting the service, it will fail stating "Unable to access 'default.path.data' (/var/lib/elasticsearch)" which is the distribution's preferred location, but was removed to prevent trouble.

Seems there are still some remnants after the #23981 cleanup.

@jasontedor
Copy link
Member

There should be an underlying cause, for example a filesystem permissions issue. This is expected though. If we can’t access the directory, we can’t verify the problem in #23981 is not present, so we fail. You need to read the cause and fix the problem. This is not a bug.

@andreas-p
Copy link
Author

IMHO trying to access a directory that is configured away by path.data is a bug.
The workaround was to create a read-only the directory /var/lib/elasticsearch again.

@jasontedor
Copy link
Member

In 5.6 it’s not a bug because we are trying to verify whether or not the consequences of a previous bug are present. The system is operating as intended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants