Skip to content

Updating SEAL Elastic Stack


Caution - direct update

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

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

Checking Indices

  1. In a browser, Start Elastic Upgrade Assistant and follow the instructions:

    http://localhost:5601/app/management/stack/upgrade_assistant/overview
    

    Elastic Upgrade Assistant will check for indices of your current version which need to be re-indexed with version 7.17 or deleted. Otherwise these indices will not work in 8.x versions.

    For details on re-indexing indices, see below.

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

  2. 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. For detail on this, see Updating SEAL Elastic Stack with New Installation.

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

Hint - automatic configuration

SEAL Elastic Stack 8.x provides an automatic configuration, see Automatic Configuration.


Re-indexing Indices

If you update to the next major version, use Elasticsearch Upgrade Helper for re-indexing.

If you prefer a manual re-indexing, procede as follows:

  1. Change to the following directory:

    cd "/opt/seal/seal-elasticstack-configuration"
    
  2. 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 can still 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

  1. 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.

  2. Download the SEAL Elastic Stack - 8.19.24.551 - rpm folder. It is saved as SEAL Elastic Stack - 8.19.24.551 - rpm.zip.

  3. Extract SEAL Elastic Stack - 8.19.24.551 - rpm.zip:

    unzip "SEAL Elastic Stack - 8.19.24.551 - rpm.zip"
    
  4. Change to the SEAL Elastic Stack - 8.19.24.551 - rpm/server directory and start installing the packages:

    cd "SEAL Elastic Stack - 8.19.24.551 - rpm/server"
    
    sudo sh install.sh
    
  5. Open the required firewall ports:

    sudo sh firewall.sh
    
  6. 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.

    Caution - breaking change in the configuration

    If you update from a SEAL Elastic Stack version 7.x, you have to transfer the new settings from the .rpmnew file manually.

    You cannot use the old .yml file, because of a breaking change in the Filebeat configuration between versions 7 and 8.

  7. Change to the configuration directory of seal-elasticsearch:

    cd /opt/seal/etc/config/seal-elasticsearch
    
  8. 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.

  9. Change to the common configuration directory:

    cd /opt/seal/etc/config
    
  10. 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.

  11. 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.

  12. Start Elasticsearch:

    sudo systemctl start seal-elasticsearch
    
  13. 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.

  14. Update the necessary database configuration as described in Configuration via Script.

  15. In Kibana, check whether the dashboards have been overwritten correctly. Delete old dashboards, if they are still existing.


Back to top