SUSE Configuration Changes¶
The deployment guide currently addresses installation in a Redhat based environment. There are a couple of issues installing Elasticsearch and ActiveMQ on SUSE. Below are some instructions on how to install these two on SUSE.
When installing ActiveMQ you might see the following error.
Configuration variable JAVA_HOME or JAVACMD is not defined correctly.
For some reason ActiveMQ isn’t properly using the system Java that is set. To fix this issue I had to set the JAVA_HOME directly.
- Edit /etc/default/activemq and set JAVA_HOME at the bottom
- Restart ActiveMQ (service activemq restart)
RPM installation isn’t supported on SUSE. To work around this issue we created a custom init.d service script and wrote up a manual procedure to install Elasticsearch on a single node.
We have created a service script to make it easy to start and stop Elasticsearch, as well as leverage chkconfig to automatically start Elasticsearch when booting up the machine. Below are the instructions on how we installed Elasticsearch on a SUSE box.
- Make sure Elasticsearch service user/group exists
- mkdir /opt/elasticsearch
- cd /opt/elasticsearch
- mv /tmp/elasticsearch-2.3.5.tar.gz
- tar -xvf elasticsearch-2.3.5.tar.gz
- rm elasticsearch-2.3.5.tar.gz
- ln -s elasticsearch-2.3.5 current
- cp elasticsearch.yml elasticsearch.yml.orig
- Modify elasticsearch.yml if you want to change the cluster name. Our copy that is installed the wizard scripts is located in /opt/kylo/setup/elasticsearch
- chown -R elasticsearch:elasticsearch /opt/elasticsearch/
- vi /etc/init.d/elasticsearch - paste in the values from /opt/kylo/setup/elasticsearch/init.d/sles/elasticsearch
- Uncomment and set the java home on line 44 of the init.d file in step #10
- chmod 755 /etc/init.d/elasticsearch
- chkconfig elasticsearch on
- service elasticsearch start