Configuring the Management Server¶
If you have installed PLOSSYS 5 with a separate management server or in a cluster, perform the following configuration steps on the management server.
Configuring Elasticsearch¶
- 
On the management server, edit the following file: /etc/elasticsearch/elasticsearch.yml
- 
Add the following lines: network.host: "0.0.0.0" discovery.type: "single-node"
- 
Save the file. 
- 
Set Max_Heap_Sizeto at least 50 % of the server's RAM:export JAVA_OPTS="-Xmx<ZZ>M -Xms<ZZ>M"Example - 2048 MB export JAVA_OPTS="-Xmx2048m -Xms2048m"Caution - value <ZZ>is the amount of RAM in Megabyte. You have to set–Xmx<ZZ>mand–Xms<ZZ>mto the same value, otherwise Elasticserach will not start.
- 
Open an editor with an empty file: sudo systemctl edit elasticsearch.service
- 
Configure the restart of the Elasticsearchservice in case of failure by adding the following lines to the file:[Service] Restart=always RestartSec=60
- 
Save the file. 
- 
Restart Elasticsearch: sudo systemctl restart elasticsearch
Configuring Kibana¶
- 
In the /opt/seal/etc/kibana.ymlfile, activate the following setting:server.host: "0.0.0.0"
- 
Restart Kibana: sudo systemctl restart seal-kibana
Adding 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 
- 
Starting and stopping the PLOSSYS 5 services 
The PLOSSYS 5 administrator (seal) has to be a member of the elasticsearch user group, too, to able to open the Elasticsearch log files.
Execute the following command to add a user to the necessary user groups:
sudo usermod --append --groups seal,elasticsearch seal