Updating SEAL Elastic Stack¶

Overview¶

The update consists of a server and a client part which you have to update separately.

Server:

The server part includes Elasticsearch and Kibana. You have to update it on the management server.
Client:

The client part contains Filebeat. You have to update it on any client server, e. g. PLOSSYS Output Engine, PLOSSYS 4, SEAL Operator, ...

Hint - running Filebeat

Filebeat has to be running, when you start the update.

For a few seconds during the update, it may happen that log files are created, which are stored in Elasticsearch neither by the old nor by the new Filebeat service.

Caution - direct update

A direct update to version 8.x requires a version 7.17.x.

If you still work with a version 7.16.x or previous versions, you have to update to version 7.17.5 first.

Preparing the Update¶

Start Elastic Upgrade Assistant.

Elastic Upgrade Assistant will check for indices of version 6.x which need to be reindexed with version 7.x or deleted. Otherwise these indices will not work in 8.x and later versions.

For details on reindexing indices, see below.

You do not need this check, if you update from one version 8.x to another version 8.x.
Create a complete backup.

Hint - new server

Making a complete backup and using a new server for a new installation of version 8.x might keep you from installing an interim version.

You need a new server for this, but you can use the automatic configuration of the security.

Reindexing Indices¶

Change to the following directory:

cd "/opt/seal/seal-elasticstack-configuration"

Start the following script:

sudo ./node/node ./configuration/scripts/reindex_accounting_data.js -url <elasticUrl e.g. https://localhost:9200> -u <credentials e.g. elastic:password>

Notes on Activating the Security¶

Hint - Unconfigured security in the old system

If your previous installation did not include an active security configuration, the installation script explicitly deactivates the security settings. You will receive a corresponding notification during the installation.

In this case the script is unable to configure the security settings automatically. You still can configure it manually later.

Hint - Preconfigured security in the new system

If you configure the security settings in your system before you update your SEAL Elastic Stack installation, the installation script will leave your settings untouched. This means that Elasticsearch will run without SSL.

Management Server¶

In a browser, log on to the SEAL Systems delivery platform with your logon data:

https://delivery.sealsystems.de

Hint - logon data

You receive the logon data from your Technical Project Manager at SEAL Systems.
Download the SEAL Elastic Stack - 8.17.3.396 - rpm folder. It is saved as SEAL Elastic Stack - 8.17.3.396 - rpm.zip.

Extract SEAL Elastic Stack - 8.17.3.396 - rpm.zip:

unzip "SEAL Elastic Stack - 8.17.3.396 - rpm.zip"

Change to the SEAL Elastic Stack - 8.17.3.396 - rpm/server directory and start installing the packages:
```
cd "SEAL Elastic Stack - 8.17.3.396 - rpm/server"
```
```
sudo sh install.sh
```
Open the required firewall ports for necessary services:
```
sudo sh firewall.sh
```
Check the configuration files:

The installation script also checks for the presence of *.rpmnew and *.rmpsave files.
- *.rpmnew files contain the latest default configurations of the updated software.
- *.rmpsave files are configuration files that are kept after the old software is uninstalled. You can use them to restore the configuration of the previous version after you have installed the new package.
You have to transfer the configuration settings from these files manually.
Change to the configuration directory of seal-elasticsearch:
```
cd /opt/seal/etc/config/seal-elasticsearch
```
In an editor, compare the elasticsearch.yml configuration file to the old elasticsearch.yml.install-bak configuration file.

Add your customer-specific changes, e. g. network.host, path.repo or xpack.security.enabled.

For details on the general configuration, see Configuring Elasticsearch.
Change to the common configuration directory:
```
cd /opt/seal/etc/config
```
In an editor, compare the kibana.yml configuration file to the old kibana.yml.install-bak configuration file.

Add your customer-specific changes, e. g. server.host, elasticsearch.username or elasticsearch.password.
Set path.data to the correct value, if necessary.
```
path.data: "${ProgramData}/SEAL Systems/data/seal-kibana"
```
Hint - path.data setting moved

In preparation for future versions, path.data is set in the kibana.yml file instead of the service configuration.

For details on the general configuration, see Configuring Kibana.

Start Elasticsearch:

sudo systemctl start seal-elasticsearch

Start Kibana:
```
sudo systemctl start seal-kibana
```
Hint - long duration

If you start Kibana for the first time after the update, this may take very long. Do not stop the starting process, just wait until it is finished.

Hint - Kibana not starting

If Kibana does not start after having been updated, see Deprecated Configuration or Insufficient Hard Disk Space for a possible solution.
Update the necessary database configuration as described in Configuration via Script.

PLOSSYS Output Engine Server¶

Caution - SEAL Elastic Stack incompatible to seal-elk

SEAL Elastic Stack contains the new version of Elasticsearch and Kibana and replaces seal-elk. Before installing SEAL Elastic Stack, you have to uninstall seal-elk:

RHEL:
```
sudo yum --assumeyes remove seal-elk
```

SLES:

sudo zypper --non-interactive remove seal-elk

In a browser, log on to the SEAL Systems delivery platform with your logon data:

https://delivery.sealsystems.de

Hint - logon data

You receive the logon data from your Technical Project Manager at SEAL Systems.
Download the SEAL Elastic Stack - 8.17.3.396 - rpm folder. It is saved as SEAL Elastic Stack - 8.17.3.396 - rpm.zip.

Extract SEAL Elastic Stack - 8.17.3.396 - rpm.zip:

unzip "SEAL Elastic Stack - 8.17.3.396 - rpm.zip"

Change to the SEAL Elastic Stack - 8.17.3.396 - rpm/client directory and install the packages:
```
cd "SEAL Elastic Stack - 8.17.3.396 - rpm/client"
```
```
sudo sh install.sh
```
Change to the configuration directory:
```
cd /opt/seal/etc
```
Check the configuration files:

The installation script also checks for the presence of *.rpmnew and *.rmpsave files.
- *.rpmnew files contain the latest default configurations of the updated software.
- *.rmpsave files are configuration files that are kept after the old software is uninstalled. You can use them to restore the configuration of the previous version after you have installed the new package.
You have to transfer the configuration settings from these files manually.
In an editor, compare the latest filebeat.yml.rpmnew default configuration file to the current filebeat.yml configuration file.

Add your customer-specific changes, e. g. output.elasticsearch.hosts and with activated security output.elasticsearch.username and output.elasticsearch.password.

For details on the general configuration, see Logging or Configuring Filebeat.
Start SEAL Filebeat:
```
sudo systemctl start seal-filebeat
```

PLOSSYS 4 Server¶

In a browser, log on to the SEAL Systems delivery platform with your logon data:

https://delivery.sealsystems.de

Hint - logon data

You receive the logon data from your Technical Project Manager at SEAL Systems.
Download the SEAL Elastic Stack - 8.17.3.396 - rpm folder. It is saved as SEAL Elastic Stack - 8.17.3.396 - rpm.zip.

Extract SEAL Elastic Stack - 8.17.3.396 - rpm.zip:

unzip "SEAL Elastic Stack - 8.17.3.396 - rpm.zip"

Change to the SEAL Elastic Stack - 8.17.3.396 - rpm/client-p4 directory and start installing the packages:
```
cd "SEAL Elastic Stack - 8.17.3.396 - rpm/client-p4"
```
```
sudo sh install.sh
```
Change to the configuration directory:
```
cd /opt/seal/etc
```
Check the configuration files:

The installation script also checks for the presence of *.rpmnew and *.rmpsave files.
- *.rpmnew files contain the latest default configurations of the updated software.
- *.rmpsave files are configuration files that are kept after the old software is uninstalled. You can use them to restore the configuration of the previous version after you have installed the new package.
You have to transfer the configuration settings from these files manually.
In an editor, compare the latest filebeat-p4-accounting.yml.rpmnew default configuration file to the current filebeat-p4-accounting.yml configuration file.

Add your customer-specific changes, e. g. output.elasticsearch.hosts and with activated security output.elasticsearch.username and output.elasticsearch.password.

For details on the general configuration, see Logging or Configuring Filebeat.

Start SEAL Filebeat:

sudo systemctl start seal-p4-accounting-filebeat

SEAL Operator Server¶

In a browser, log on to the SEAL Systems delivery platform with your logon data:

https://delivery.sealsystems.de

Hint - logon data

You receive the logon data from your Technical Project Manager at SEAL Systems.
Download the SEAL Elastic Stack - 8.17.3.396 - rpm folder. It is saved as SEAL Elastic Stack - 8.17.3.396 - rpm.zip.

Extract SEAL Elastic Stack - 8.17.3.396 - rpm.zip:

unzip "SEAL Elastic Stack - 8.17.3.396 - rpm.zip"

Change to the SEAL Elastic Stack - 8.17.3.396 - rpm/client-operator directory and start installing the packages:
```
cd "SEAL Elastic Stack - 8.17.3.396 - rpm/client-operator"
```
```
sudo sh install.sh
```
Change to the configuration directory:
```
cd /opt/seal/etc
```
Check the configuration files:

The installation script also checks for the presence of *.rpmnew and *.rmpsave files.
- *.rpmnew files contain the latest default configurations of the updated software.
- *.rmpsave files are configuration files that are kept after the old software is uninstalled. You can use them to restore the configuration of the previous version after you have installed the new package.
You have to transfer the configuration settings from these files manually.
In an editor, compare the latest filebeat-operator.yml.rpmnew default configuration file to the current filebeat-operator.yml configuration file.

Add your customer-specific changes, e. g. output.elasticsearch.hosts and with activated security output.elasticsearch.username and output.elasticsearch.password.

For details on the general configuration, see Logging or Configuring Filebeat.

Start SEAL Filebeat:

sudo systemctl start seal-operator-filebeat

PLOSSYS Distribution Engine/DPF Server¶

In a browser, log on to the SEAL Systems delivery platform with your logon data:

https://delivery.sealsystems.de

Hint - logon data

You receive the logon data from your Technical Project Manager at SEAL Systems.
Download the SEAL Elastic Stack - 8.17.3.396 - rpm folder. It is saved as SEAL Elastic Stack - 8.17.3.396 - rpm.zip.

Extract SEAL Elastic Stack - 8.17.3.396 - rpm.zip:

unzip "SEAL Elastic Stack - 8.17.3.396 - rpm.zip"

Change to the SEAL Elastic Stack - 8.17.3.396 - rpm/client-dpf directory and start installing the packages:
```
cd "SEAL Elastic Stack - 8.17.3.396 - rpm/client-dpf"
```
```
sudo sh install.sh
```
Change to the configuration directory:
```
cd /opt/seal/etc
```
Check the configuration files:

The installation script also checks for the presence of *.rpmnew and *.rmpsave files.
- *.rpmnew files contain the latest default configurations of the updated software.
- *.rmpsave files are configuration files that are kept after the old software is uninstalled. You can use them to restore the configuration of the previous version after you have installed the new package.
You have to transfer the configuration settings from these files manually.
In an editor, compare the latest filebeat-dpf.yml.rpmnew default configuration file to the current filebeat-dpf.yml configuration file.

Add your customer-specific changes, e. g. output.elasticsearch.hosts and with activated security output.elasticsearch.username and output.elasticsearch.password.

For details on the general configuration, see Logging or Configuring Filebeat.
Start SEAL Filebeat:
```
sudo systemctl start seal-dpf-filebeat
```