Configure the Management Server¶
Perform the following configuration steps on the management server if you have installed PLOSSYS 5 with separate management server or in a cluster.
Configure Elasticsearch¶
-
Edit the following file on the management server:
/etc/elasticsearch/elasticsearch.yml
-
Add the following lines:
network.host: 0.0.0.0 discovery.type: single-node
-
Save the file.
-
Set
Max_Heap_Size
to at least 50 % of the server's RAM.$export JAVA_OPTS="-Xmx<ZZ>M -Xms<ZZ>M"
Hint - value
<ZZ>
is the amount of RAM in Megabytes.–Xmx<ZZ>m
and–Xms<ZZ>m
have to be set to the same value, otherwise Elasticserach will not start.Example - 2048 MB
$export JAVA_OPTS="-Xmx2048m -Xms2048m"
-
Execute the following command. It opens an editor with an empty file.
sudo systemctl edit elasticsearch.service
-
Add the following lines to the file:
[Service] Restart=always RestartSec=60
-
Save the file.
-
Restart the service for Elasticsearch:
sudo systemctl restart elasticsearch
Configure Kibana¶
-
In the
/opt/seal/etc/kibana.yml
file, activate the following setting:server.host: 0.0.0.0
-
Restart the following service for Kibana:
sudo systemctl restart seal-kibana
Add the seal
User to the elasticsearch
Group¶
During the installation, the seal
user and the seal
user group are created. All PLOSSYS 5 services are started with the seal
user. All users of the seal
user group have the following privileges:
- Modifying the configuration files
- Accessing the log files
- Stopping and starting PLOSSYS 5 services
For being able to open the Elasticsearch log files, the PLOSSYS 5 administrator (seal
) has to be a member of the elasticsearch
user group, too.
Execute the following command to add a user to the necessary user groups:
sudo usermod --append --groups seal,elasticsearch seal
Next Step¶
Continue with: Configure the PLOSSYS 5 Server