publish_address ]]Īt .TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:328)Īt .TransportClientNodesService.execute(TransportClientNodesService.java:226)Īt .TransportProx圜lient.execute(TransportProx圜lient.java:59)Īt .TransportClient.doExecute(TransportClient.java:345)Īt .AbstractClient.execute(AbstractClient.java:403)Īt .AbstractClient.execute(AbstractClient.java:392)Īt .AbstractClient$ClusterAdmin.execute(AbstractClient.java:704)Īt .AbstractClient$ClusterAdmin.health(AbstractClient.java:726)Īt .SearchGuardAdmin.generateDiagnoseTrace(SearchGuardAdmin.java:676)Īt .SearchGuardAdmin.main0(SearchGuardAdmin.java:369)Īt .SearchGuardAdmin.main(SearchGuardAdmin. _hostname: trueĪfter this, I could restart my node, checking the cluster state is YELLOW and Searchguard is properly recognized: RESTART YOUR SERVER FOR THE CHANGES TO TAKE EFFECT If you do not restart your server, the name will not change, and you will not be able to find it. Then I copied truststore.jks and node1-keystore.jks to the ES config directory and edited elasticsearch.yml as shown below: Take note as to whether or not you have a password set. gen_client_node_cert.sh node1 m圜Apass mypass gen_root_ca.sh truestore.jks m圜Apass mypass I initially generated both truststore.jks and keystore.jks files, using gen_root_ca.sh and gen_client_node_cert.sh respectively, this way: I followed the documentation in order to set up search guard in a testing single-node ES cluster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |