# None of the configured nodes are available

**URL:** <https://forum.search-guard.com/t/none-of-the-configured-nodes-are-available/423>\
**Category:** Search Guard\
**Created:** [March 23, 2017, 8:02pm UTC](https://forum.search-guard.com/t/none-of-the-configured-nodes-are-available/423 "2017-03-23T20:02:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Maikel\_Ortega\_Hernandez](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@Maikel\_Ortega\_Hernandez](https://forum.search-guard.com/u/Maikel_Ortega_Hernandez)\
**Post date:** [March 23, 2017, 8:02pm UTC](https://forum.search-guard.com/t/none-of-the-configured-nodes-are-available/423/1 "2017-03-23T20:02:39Z")

</div>

Hello everyone i tried to use search guard using the example.sh to generate keystore and certificates, but when i try to initialize sgadmin i get this message

./sgadmin.sh -ts truststore.jks -tspass changeit -ks kirk-keystore.jks -kspass changeit -cd …/sgconfig -cn nodo -nhnv  
Search Guard Admin v5  
Will connect to localhost:9300 … done  
Contacting elasticsearch cluster ‘nodo’ and wait for YELLOW clusterstate …  
Cannot retrieve cluster state due to: None of the configured nodes are available: [{#transport#-1}{aZaCLBM1TG693peAfvIEdw}{localhost}{127.0.0.1:9300}]. This is not an error, will keep on trying …

- Try running sgadmin.sh with -icl and -nhnv (If thats works you need to check your clustername as well as hostnames in your SSL certificates)
- If this is not working, try running sgadmin.sh with --diagnose and see diagnose trace log file)

i already try with -icl parameter the same result. i attach elasticsearch.yml and diagnostic log from sgadmin and also elastic log (nodo.log).

any idea… thanks a lot in advantage

[sgadmin\_diag\_trace\_2017-Mar-16\_20-04-50.txt](https://forum.search-guard.com/uploads/short-url/itLPhamfWSEwTyZauxzfyM7E1aH.txt) (13.3 KB)

[sgadmin\_diag\_trace\_2017-Mar-16\_20-06-39.txt](https://forum.search-guard.com/uploads/short-url/vtu6hLcD4sJx74qKhKuXw1HdpBu.txt) (13.3 KB)

[elasticsearch.yml](https://forum.search-guard.com/uploads/short-url/es30XS8CztsARNShYWjXexsdW1Z.yml) (4.55 KB)

[nodo.log](https://forum.search-guard.com/uploads/short-url/a48yz6oyFZqugAhNAiCKzR5OXxM.log) (26.4 KB)

---

<div class="post-metadata">

**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\
**Post date:** [March 23, 2017, 8:41pm UTC](https://forum.search-guard.com/t/none-of-the-configured-nodes-are-available/423/2 "2017-03-23T20:41:06Z")

</div>

This commands loo correct  
./sgadmin.sh -ts truststore.jks -tspass changeit -ks kirk-keystore.jks -kspass changeit -cd ../sgconfig -cn nodo -nhnv  
./sgadmin.sh -ts truststore.jks -tspass changeit -ks kirk-keystore.jks -kspass changeit -cd ../sgconfig -icl -nhnv

but there are a few other thing which are strange:

1) Pls run elasticsearch as well as sgadmin with java 8 and not java 9 which ist not released and not supported yet  
2) network.host: [192.168.3.113,127.0.0.1] in elasticsearch.yml makes no sense, this should be a single hostname/ip and not an array (and even then it had to look like ["192.168.3.113","127.0.0.1"] )  
3) The diagnose trace show that you executed sgadmin like that: "-ts truststore.jks -tspass changeit -ks kirk-keystore.jks -kspass changeit -cd ../sgconfig -cn icl -nhnv --diagnose" which is indeed wrong

You can also try our bundle [GitHub - floragunncom/search-guard: Search Guard Plugin - Security for Elasticsearch](https://github.com/floragunncom/search-guard/wiki/Search-Guard-Bundle)

> **···**
>
> > Am 23.03.2017 um 21:02 schrieb Maikel Ortega Hernández \<maikeloh@gmail.com\>:
> > 
> > Hello everyone i tried to use search guard using the example.sh to generate keystore and certificates, but when i try to initialize sgadmin i get this message
> > 
> > ./sgadmin.sh -ts truststore.jks -tspass changeit -ks kirk-keystore.jks -kspass changeit -cd ../sgconfig -cn nodo -nhnv  
> > Search Guard Admin v5  
> > Will connect to localhost:9300 ... done  
> > Contacting elasticsearch cluster 'nodo' and wait for YELLOW clusterstate ...  
> > Cannot retrieve cluster state due to: None of the configured nodes are available: [{#transport#-1}{aZaCLBM1TG693peAfvIEdw}{localhost}{127.0.0.1:9300}]. This is not an error, will keep on trying ...  
> > &nbsp;&nbsp;&nbsp;\* Try running sgadmin.sh with -icl and -nhnv (If thats works you need to check your clustername as well as hostnames in your SSL certificates)  
> > &nbsp;&nbsp;&nbsp;\* If this is not working, try running sgadmin.sh with --diagnose and see diagnose trace log file)
> > 
> > i already try with -icl parameter the same result. i attach elasticsearch.yml and diagnostic log from sgadmin and also elastic log (nodo.log).
> > 
> > any idea.. thanks a lot in advantage
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups "Search Guard" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an email to search-guard+unsubscribe@googlegroups.com.  
> > To post to this group, send email to search-guard@googlegroups.com.  
> > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/61b13fd5-1b7a-4cfe-81e3-b305e228f434%40googlegroups.com\](https://groups.google.com/d/msgid/search-guard/61b13fd5-1b7a-4cfe-81e3-b305e228f434%40googlegroups.com%5C).  
> > For more options, visit [https://groups.google.com/d/optout\](https://groups.google.com/d/optout%5C).  
> > \<sgadmin\_diag\_trace\_2017-Mar-16\_20-04-50.txt\>\<sgadmin\_diag\_trace\_2017-Mar-16\_20-06-39.txt\>\<elasticsearch.yml\>\<nodo.log\>

---

<div class="post-metadata">

**Author:** ![Maikel\_Ortega\_Hernandez](https://avatars.discourse-cdn.com/v4/letter/m/2bfe46/32.png) [@Maikel\_Ortega\_Hernandez](https://forum.search-guard.com/u/Maikel_Ortega_Hernandez)\
**Post date:** [March 25, 2017, 1:50am UTC](https://forum.search-guard.com/t/none-of-the-configured-nodes-are-available/423/3 "2017-03-25T01:50:32Z")

</div>

java 9 was that cause the error, thanks a lot for the answer

> **···**
>
> El jueves, 23 de marzo de 2017, 15:41:07 (UTC-5), Search Guard escribió:
> 
> > This commands loo correct
> > 
> > ./sgadmin.sh -ts truststore.jks -tspass changeit -ks kirk-keystore.jks -kspass changeit -cd …/sgconfig -cn nodo -nhnv
> > 
> > ./sgadmin.sh -ts truststore.jks -tspass changeit -ks kirk-keystore.jks -kspass changeit -cd …/sgconfig -icl -nhnv
> > 
> > but there are a few other thing which are strange:
> > 
> > 1. Pls run elasticsearch as well as sgadmin with java 8 and not java 9 which ist not released and not supported yet
> > 
> > 2. network.host: [192.168.3.113,127.0.0.1] in elasticsearch.yml makes no sense, this should be a single hostname/ip and not an array (and even then it had to look like [“192.168.3.113”,“127.0.0.1”] )
> > 
> > 3. The diagnose trace show that you executed sgadmin like that: “-ts truststore.jks -tspass changeit -ks kirk-keystore.jks -kspass changeit -cd …/sgconfig -cn icl -nhnv --diagnose” which is indeed wrong
> > 
> > You can also try our bundle [https://github.com/floragunncom/search-guard/wiki/Search-Guard-Bundle](https://github.com/floragunncom/search-guard/wiki/Search-Guard-Bundle)
> > 
> > > Am 23.03.2017 um 21:02 schrieb Maikel Ortega Hernández [maik...@gmail.com](mailto:maik...@gmail.com):
> > 
> > > Hello everyone i tried to use search guard using the example.sh to generate keystore and certificates, but when i try to initialize sgadmin i get this message
> > > 
> > > ./sgadmin.sh -ts truststore.jks -tspass changeit -ks kirk-keystore.jks -kspass changeit -cd …/sgconfig -cn nodo -nhnv
> > 
> > > Search Guard Admin v5
> > 
> > > Will connect to localhost:9300 … done
> > 
> > > Contacting elasticsearch cluster ‘nodo’ and wait for YELLOW clusterstate …
> > 
> > > Cannot retrieve cluster state due to: None of the configured nodes are available: [{#transport#-1}{aZaCLBM1TG693peAfvIEdw}{localhost}{127.0.0.1:9300}]. This is not an error, will keep on trying …
> > 
> > > - Try running sgadmin.sh with -icl and -nhnv (If thats works you need to check your clustername as well as hostnames in your SSL certificates)
> > 
> > > - If this is not working, try running sgadmin.sh with --diagnose and see diagnose trace log file)
> > 
> > > i already try with -icl parameter the same result. i attach elasticsearch.yml and diagnostic log from sgadmin and also elastic log (nodo.log).
> > 
> > > any idea… thanks a lot in advantage
> > 
> > > –  
> > > You received this message because you are subscribed to the Google Groups “Search Guard” group.
> > 
> > > To unsubscribe from this group and stop receiving emails from it, send an email to [search-guard...@googlegroups.com](mailto:search-guard...@googlegroups.com).
> > 
> > > To post to this group, send email to [search...@googlegroups.com](mailto:search...@googlegroups.com).
> > 
> > > To view this discussion on the web visit [https://groups.google.com/d/msgid/search-guard/61b13fd5-1b7a-4cfe-81e3-b305e228f434%40googlegroups.com](https://groups.google.com/d/msgid/search-guard/61b13fd5-1b7a-4cfe-81e3-b305e228f434%40googlegroups.com).
> > 
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > 
> > > \<sgadmin\_diag\_trace\_2017-Mar-16\_20-04-50.txt\>\<sgadmin\_diag\_trace\_2017-Mar-16\_20-06-39.txt\>\<elasticsearch.yml\>\<nodo.log\>
