Arch Linux

bjo

Member

Registered: 2011-09-10

Posts: 83

[SOLVED] elasticsearch remains unhealthy

Hi,

since some days my elasticsearch node used for Mastodon und Nextcloud is unhealthy. I moved the whole system some days ago, so maybe the data is bricked -  let's clean /var/lib/elasticsearch and start from scratch.  But no, it still remainds unhealthy. According to the logs,  the startup is fine and it's single node has joined the cluster: https://p.rrbone.net/?91a4b614e2430fe3# … RSAFjubizv
But even running "elasticsearch-setup-passwords auto" fails:

Your cluster health is currently RED.
This means that some cluster data is unavailable and your cluster is not fully functional.

It is recommended that you resolve the issues with your cluster before running elasticsearch-setup-passwords.
It is very likely that the password changes will fail when run against an unhealthy cluster.

Do you want to continue with the password setup process [y/N]y

******************************************************************************
Note: The 'elasticsearch-setup-passwords' tool has been deprecated. This       command will be removed in a future release.
******************************************************************************

Initiating the setup of passwords for reserved users elastic,apm_system,kibana,kibana_system,logstash_system,beats_system,remote_monitoring_user.
The passwords will be randomly generated and printed to the console.
Please confirm that you would like to continue [y/N]y


Unexpected response code [503] from calling PUT http://127.0.0.1:9200/_security/user/apm_system/_password?pretty
Cause: Cluster state has not been recovered yet, cannot write to the [null] index

Possible next steps:
* Try running this tool again.
* Try running with the --verbose parameter for additional messages.
* Check the elasticsearch logs for additional error details.
* Use the change password API manually. 


ERROR: Failed to set password for user [apm_system]., with exit code 75

Some other solutions from https://www.elastic.co/guide/en/elastic … tatus.html also fail - because the node is unhealthy.

Edit:
Stumpled upon https://github.com/elastic/elasticsearch/issues/103963 and then tried to use openjdk 17 instead of openjdk 21. Now it works!

Last edited by bjo (2024-01-20 22:15:53)