A relatively typical error when installing a single node Elastic Elasticsearch software is when the passwords are set:
[root@loganalyzer elasticsearch]# ./bin/elasticsearch-setup-passwords -v auto 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 Connection failure to: http://192.168.0.4:9200/_security/user/apm_system/_password?pretty failed: Read timed out ERROR: Failed to set password for user [apm_system].
Such error may prevent the initial password setting of several important passwords and compromise the Elasticsearch software security model. Even including the
in the /etc/elasticsearch/elasticsearch.yml would lead to such error. The missing option in the configuration /etc/elasticsearch/elasticsearch.yml is:
By default, this option is commented out and it should be set on initial installation, though it is not required when starting the elasticsearch node (with no security model enabled)!
This is an array with all the servers’ hostnames in the cluster setup. In single-node mode, this option (discovery.seed_hosts) should be set only to the hostname of the single node like in this case “node-1”. This is the hostname of the server. The user must include the user’s current server hostname, not this example name “node-1”!
Setting the right hostname for discovery.seed_hosts in /etc/elasticsearch/elasticsearch.yml would let the user to set all password with the Elasticsearch tool elasticsearch-setup-passwords
The error may occur in a cluster setup with multiple servers, too, if the hosts are not filled in this option – discovery.seed_hosts.
Here is what to expect when executing elasticsearch-setup-passwords (even with some RED indexes):
[root@loganalyzer ~]# cd /usr/share/elasticsearch/ [root@loganalyzer elasticsearch]# ./bin/elasticsearch-setup-passwords -v auto 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 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 Changed password for user apm_system PASSWORD apm_system = judakai2Wai9Saiph8ah Changed password for user kibana_system PASSWORD kibana_system = eisiadit3CieG4Requie Changed password for user kibana PASSWORD kibana = bi3NohquohLoonaizei1 Changed password for user logstash_system PASSWORD logstash_system = AhC2kue5eeR4eK1LeeZa Changed password for user beats_system PASSWORD beats_system = reeyu8ooj8Eebee5ni2c Changed password for user remote_monitoring_user PASSWORD remote_monitoring_user = aeshahx9Ohkoph3rai6a Changed password for user elastic PASSWORD elastic = beiPhei4xu5iXailocei
No errors and the password are set successfully.