# Reg the Opensearch cluster setup from Linux Server(rpm) **URL:** \ **Category:** Security\ **Tags:** configure, install\ **Created:** [February 27, 2023, 11:06am UTC](https://forum.opensearch.org/t/reg-the-opensearch-cluster-setup-from-linux-server-rpm/12689 "2023-02-27T11:06:04Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ashokfredrick](https://avatars.discourse-cdn.com/v4/letter/a/f9ae1b/32.png) [@ashokfredrick](https://forum.opensearch.org/u/ashokfredrick)\ **Post date:** [February 27, 2023, 11:06am UTC](https://forum.opensearch.org/t/reg-the-opensearch-cluster-setup-from-linux-server-rpm/12689/1 "2023-02-27T11:06:04Z")
**Versions** (relevant - OpenSearch/Dashboard/Server OS/Browser): Opensearch 2.3.0 RHEL 8 RPM installation **Describe the issue** : Hi Team, I’m trying to setup a opensearch cluster and followed the steps based on the below link. > **[Creating a cluster](https://docs.opensearch.org/latest/tuning-your-cluster/cluster/)** > > Creating a cluster But while run the securityadmin.sh it’s keep on running with the below info. Please advise. # Getting the below while run the securityadmin.sh [root@osd\_server1 opensearch]# bash /usr/share/opensearch/plugins/opensearch-security/tools/securityadmin.sh -icl -nhnv -ts /etc/opensearch/opensearch.truststore.jks -tspass PASSWORD -ks /etc/opensearch/opensearch.keystore.jks -kspass PASSWORD * * * \*\* This tool will be deprecated in the next major release of OpenSearch \*\* \*\* [[DEPRECATION] Security Plugin Tools will be replaced · Issue #1755 · opensearch-project/security · GitHub](https://github.com/opensearch-project/security/issues/1755) \*\* * * * WARNING: nor OPENSEARCH\_JAVA\_HOME nor JAVA\_HOME is set, will use /usr/bin/java Security Admin v7 Will connect to localhost:9200 ERR: Seems there is no OpenSearch running on localhost:9200 - Will exit [root@osd\_server1 opensearch]# vim /etc/opensearch/opensearch.yml [root@osd\_server1 opensearch]# systemctl restart opensearch [root@osd\_server1 opensearch]# bash /usr/share/opensearch/plugins/opensearch-security/tools/securityadmin.sh -icl -nhnv -ts /etc/opensearch/opensearch.truststore.jks -tspass PASSWORD -ks /etc/opensearch/opensearch.keystore.jks -kspass PASSWORD * * * \*\* This tool will be deprecated in the next major release of OpenSearch \*\* \*\* [[DEPRECATION] Security Plugin Tools will be replaced · Issue #1755 · opensearch-project/security · GitHub](https://github.com/opensearch-project/security/issues/1755) \*\* * * * WARNING: nor OPENSEARCH\_JAVA\_HOME nor JAVA\_HOME is set, will use /usr/bin/java Security Admin v7 Will connect to localhost:9200 … done Connected as “CN=osd\_server1.vsi.uat.xxx.com,OU=Google,O=Google Ltd,L=Infra,C=Ind” OpenSearch Version: 2.3.0 Contacting opensearch cluster ‘opensearch’ and wait for YELLOW clusterstate … Cannot retrieve cluster state due to: 30,000 milliseconds timeout on connection http-outgoing-2 [ACTIVE]. This is not an error, will keep on trying … Root cause: java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-2 [ACTIVE] (java.net.SocketTimeoutException/java.net.SocketTimeoutException) - Try running securityadmin.sh with -icl (but no -cl) and -nhnv (If that works you need to check your clustername as well as hostnames in your TLS certificates) - Make sure that your keystore or PEM certificate is a client certificate (not a node certificate) and configured properly in opensearch.yml - If this is not working, try running securityadmin.sh with --diagnose and see diagnose trace log file) - Add --accept-red-cluster to allow securityadmin to operate on a red cluster. Cannot retrieve cluster state due to: 30,000 milliseconds timeout on connection http-outgoing-3 [ACTIVE]. This is not an error, will keep on trying … Root cause: java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-3 [ACTIVE] (java.net.SocketTimeoutException/java.net.SocketTimeoutException) - Try running securityadmin.sh with -icl (but no -cl) and -nhnv (If that works you need to check your clustername as well as hostnames in your TLS certificates) - Make sure that your keystore or PEM certificate is a client certificate (not a node certificate) and configured properly in opensearch.yml - If this is not working, try running securityadmin.sh with --diagnose and see diagnose trace log file) - Add --accept-red-cluster to allow securityadmin to operate on a red cluster. Cannot retrieve cluster state due to: 30,000 milliseconds timeout on connection http-outgoing-4 [ACTIVE]. This is not an error, will keep on trying … Root cause: java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-4 [ACTIVE] (java.net.SocketTimeoutException/java.net.SocketTimeoutException) - Try running securityadmin.sh with -icl (but no -cl) and -nhnv (If that works you need to check your clustername as well as hostnames in your TLS certificates) - Make sure that your keystore or PEM certificate is a client certificate (not a node certificate) and configured properly in opensearch.yml - If this is not working, try running securityadmin.sh with --diagnose and see diagnose trace log file) - Add --accept-red-cluster to allow securityadmin to operate on a red cluster. Cannot retrieve cluster state due to: 30,000 milliseconds timeout on connection http-outgoing-5 [ACTIVE]. This is not an error, will keep on trying … Root cause: java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-5 [ACTIVE] (java.net.SocketTimeoutException/java.net.SocketTimeoutException) - Try running securityadmin.sh with -icl (but no -cl) and -nhnv (If that works you need to check your clustername as well as hostnames in your TLS certificates) - Make sure that your keystore or PEM certificate is a client certificate (not a node certificate) and configured properly in opensearch.yml - If this is not working, try running securityadmin.sh with --diagnose and see diagnose trace log file) - Add --accept-red-cluster to allow securityadmin to operate on a red cluster. Cannot retrieve cluster state due to: 30,000 milliseconds timeout on connection http-outgoing-6 [ACTIVE]. This is not an error, will keep on trying … Root cause: java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-6 [ACTIVE] (java.net.SocketTimeoutException/java.net.SocketTimeoutException) - Try running securityadmin.sh with -icl (but no -cl) and -nhnv (If that works you need to check your clustername as well as hostnames in your TLS certificates) - Make sure that your keystore or PEM certificate is a client certificate (not a node certificate) and configured properly in opensearch.yml - If this is not working, try running securityadmin.sh with --diagnose and see diagnose trace log file) ================================================================ **Configuration** : RPM installation in Linux OS (RHEL 8), (vCpu = 8, Memory = 128gb) **Relevant Logs or Screenshots** : ---
**Author:** ![kris](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/kris/32/2208_2.png) [@kris](https://forum.opensearch.org/u/kris)\ **Post date:** [March 23, 2023, 11:51pm UTC](https://forum.opensearch.org/t/reg-the-opensearch-cluster-setup-from-linux-server-rpm/12689/2 "2023-03-23T23:51:33Z")
hello @ashokfredrick - it looks like it isn’t finding the JDK - let me know if this page of the docs helps: [Installing OpenSearch - OpenSearch documentation](https://opensearch.org/docs/latest/install-and-configure/install-opensearch/index/) (also, I edited out your password in the text) ---
**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/pablo/32/10363_2.png) [@pablo](https://forum.opensearch.org/u/pablo)\ **Post date:** [May 23, 2023, 11:07am UTC](https://forum.opensearch.org/t/reg-the-opensearch-cluster-setup-from-linux-server-rpm/12689/3 "2023-05-23T11:07:43Z")
@ashokfredrick Have you found a solution to your issue? ---
**Author:** ![cucukaka](https://avatars.discourse-cdn.com/v4/letter/c/87869e/32.png) [@cucukaka](https://forum.opensearch.org/u/cucukaka)\ **Post date:** [June 5, 2023, 1:36am UTC](https://forum.opensearch.org/t/reg-the-opensearch-cluster-setup-from-linux-server-rpm/12689/4 "2023-06-05T01:36:26Z")
I found same error. But it hasn’t been solved yet… According to the attached url page, " The OpenSearch distribution for Linux ships with a compatible [Adoptium JDK](https://adoptium.net/) version of Java in the `jdk` directory". That mean is that JDK is installed together when opensearch is installed, I don’t understand why it can’t find jdk. other setting are set the same as that page