Skip to content

Update installing-stack-demo-self.asciidoc to mitigate error-handling issue. update variable on tail command #3015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 15, 2025
Merged

Update installing-stack-demo-self.asciidoc to mitigate error-handling issue. update variable on tail command #3015

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c422dcf
Update installing-stack-demo-self.asciidoc
rich-cabrera Apr 7, 2025
f043019
nit to trigger CI
leemthompo Apr 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions docs/en/install-upgrade/installing-stack-demo-self.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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, modify your network configuration before proceeding.
====
+
[source,"shell"]
----
Expand Down Expand Up @@ -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 <CLUSTER.NAME> 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/<CLUSTER.NAME>.log
----
+
Notice in the log file some helpful diagnostics, such as:
Expand Down