I have been doing many deployment tests locally (on my computer) with success. Now, I am testing deployment onto our staging environment and have run into a blocker. sgadmin says it connects, but hangs on “waiting for cluster to turn yellow”. I’ll now explain my set up.
SG 5.5.2-16 (no enterprise modules)
ES config is NOT in
elasticsearch/configbut in a separate folder. Since the cluster existed before, this is already configured.
This cluster has 2 nodes whereas my local test cluster only had one node.
I have copied known working keystores to the ES config folder and those seem to work (as sgadmin complained when the paths were set incorrectly).
My ES config is as such:
discovery.zen.ping.unicast.hosts: [“poc-profiles-es-01”, “poc-profiles-es-02”]
- “CN=admin,OU=Comptes de services,OU=SIEGE Accounts,DC=siege,DC=np6,DC=local”
######## End Search Guard Demo Configuration ########
type: http host: ["http://127.0.0.1:9200"] auth.username: kibanaserver auth.password: kibanaserver
Now, about the problem. When I run sgadmin.sh, at the very beginning it says its connecting to my cluster at 9300 “…done”. Then it prints an SG license warning, then it says something along the lines of “Connecting to cluster ‘profiles-poc’ at localhost:9300 and waiting for YELLOW state”. Here is hangs.
I’ve read there is a diagnose flag so I turned that on. Sadly I lost the logs (and had to relinquish the servers to other workers for now), but the main problem was a “MasterNotDiscoveredException”.
Would you ladies/gentlemen have any ideas on where to start debugging this?
Please and thank you,