> Those changes will permanently enable Elasticsearch, Topbeat, and Logstash. New controllers/workers will not have these services anymore. The services are also stopped on the current workers/controllers.
Do you mean "New controllers/workers WILL have these services"?
2) In Step 5. Manually enable
#!/bin/sh
sudo update-rc.d topbeat enable
if [ -f /etc/init/tiger-logstash.conf ]; then
sudo service tiger-logstash stop || echo
else
sudo service cloudbees-logstash stop || echo
fi
sudo service topbeat stop || echo
Shouldn't the script run a "start" instead of a "stop"?
Comments
2 comments
1) Step 4. Re-Enable
> Those changes will permanently enable Elasticsearch, Topbeat, and Logstash. New controllers/workers will not have these services anymore. The services are also stopped on the current workers/controllers.
Do you mean "New controllers/workers WILL have these services"?
2) In Step 5. Manually enable
Shouldn't the script run a "start" instead of a "stop"?
Shinta,
You are right in 1) and 2). I have created an internal issue to fix the article.
In the meantime, feel free to open a support request if you need help with this.
Regards,
Please sign in to leave a comment.