Help Center/ MapReduce Service/ Component Operation Guide (LTS) (Ankara Region)/ Using Elasticsearch/ Common Issues About Elasticsearch/ What Can I Do If Elasticsearch Instance Fault Occurs Due to Insufficient Directory Permission?

Updated on 2024-11-29 GMT+08:00

View PDF

What Can I Do If Elasticsearch Instance Fault Occurs Due to Insufficient Directory Permission?

Symptom

The alarm indicating that the Elasticsearch process is faulty is displayed on Manager.

Cause Analysis

The user wants to check the error information "Unable to access path.data /srv/BigData/elasticsearch/esmaster" in the elasticsearch_cluster.log log file on the faulty Elasticsearch instance. However, the user does not have the permission on the directory of log file.

Solution

Go to the corresponding directory. It is found that the directory can only be accessed by user root. Run the following command to change the permission on the directory to omm:wheel:

chown -R omm:wheel elasticsearch
Log in to Manager and restart the faulty instance.

Parent topic: Common Issues About Elasticsearch

Previous topic: What Can I Do If Instance Startup Failure Is Caused by the Configuration File During the Elasticsearch Startup?

Next topic: What Can I Do If the Speed of Writing Data into Elasticsearch Is Slow Due to Fault on an Elasticsearch Node?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.