What Can I Do If My Custer Is Unavailable Due to an X-pack Parameter Configuration?
Symptom
The cluster status is Unavailable, and the task status of the cluster is Configuration error. Restart failed.
Possible Causes
You have configured custom X-pack parameters. CSS does not support the X-pack function.
Procedure
- On the Clusters page, click the name of the unavailable cluster. The Cluster Information page is displayed.
- Choose Parameter Configurations, expand the Customize module, and check whether custom X-pack parameters exist.
Examples of the custom X-pack parameters:
- xpack.security.enabled: true
- xpack.security.http.ssl.enabled: true
- xpack.security.http.ssl.keystore.path: "http.p12
- If yes, go to the next step.
- If no, contact technical support to locate the parameter configuration problem.
- Delete the custom X-pack parameters.
- Click Edit and click Delete on the right of the parameter you want to be delete.
- Click Submit. In the displayed Submit Configuration dialog box, select I understand that the modification will take effect after the cluster is restarted. and click OK.
If the Status is Successful in the parameter modification list, the modification has been saved.
- Return to the cluster list and choose More > Restart in the Operation column to restart the cluster and make the modification take effect.
- After the cluster is restarted, the cluster becomes available.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot