From c422dcf9d758ed85d47fae15d4580151ad264a87 Mon Sep 17 00:00:00 2001 From: rich-cabrera Date: Mon, 7 Apr 2025 11:49:13 -0400 Subject: [PATCH 1/2] Update installing-stack-demo-self.asciidoc Adding an Important clarification. The enrollment script fails without proper error handling if the second node is not able to access the first node. the elasticsearch.yml ends up modified and the enrollment script is unable to be reran without undoing all the changes. Reminder added to ensure network access is available before proceeding. second. the tail command is incorrect unless the cluster.name is also elasticsearch-demo. this value defaults to cluster.name --- .../installing-stack-demo-self.asciidoc | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/en/install-upgrade/installing-stack-demo-self.asciidoc b/docs/en/install-upgrade/installing-stack-demo-self.asciidoc index 39420348a..267790b24 100644 --- a/docs/en/install-upgrade/installing-stack-demo-self.asciidoc +++ b/docs/en/install-upgrade/installing-stack-demo-self.asciidoc @@ -305,6 +305,12 @@ Note the following tips about enrollment tokens: ==== . In the terminal shell for your second {es} node, pass the enrollment token as a parameter to the `elasticsearch-reconfigure-node` tool: +[IMPORTANT] +==== +Be sure the second node is able to access the first node before running the following command. You can test this by running a curl command to the first node at port 9200. + +If you are unable to access the first node, please modify your network configuration before proceeding. +==== + [source,"shell"] ---- @@ -352,11 +358,11 @@ network.host: 10.128.0.132 sudo systemctl start elasticsearch.service ---- -. **Optionally**, to view the progress as the second {es} node starts up and connects to the first {es} node, open a new terminal into the second node and `tail` the {es} log file: +. **Optionally**, to view the progress as the second {es} node starts up and connects to the first {es} node, open a new terminal into the second node and `tail` the {es} log file. Be sure to replace with the cluster.name you set earlier in the first node's elasticsearch.yml: + [source,"shell"] ---- -sudo tail -f /var/log/elasticsearch/elasticsearch-demo.log +sudo tail -f /var/log/elasticsearch/.log ---- + Notice in the log file some helpful diagnostics, such as: From f0430191d1eba0ec5841c265ff6153ac95f56223 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Tue, 15 Apr 2025 16:53:40 +0200 Subject: [PATCH 2/2] nit to trigger CI --- docs/en/install-upgrade/installing-stack-demo-self.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/install-upgrade/installing-stack-demo-self.asciidoc b/docs/en/install-upgrade/installing-stack-demo-self.asciidoc index 267790b24..f2bcd38b0 100644 --- a/docs/en/install-upgrade/installing-stack-demo-self.asciidoc +++ b/docs/en/install-upgrade/installing-stack-demo-self.asciidoc @@ -309,7 +309,7 @@ Note the following tips about enrollment tokens: ==== Be sure the second node is able to access the first node before running the following command. You can test this by running a curl command to the first node at port 9200. -If you are unable to access the first node, please modify your network configuration before proceeding. +If you are unable to access the first node, modify your network configuration before proceeding. ==== + [source,"shell"]