Version-Specific Upgrades

Warning

The upgrade script must be executed from within the install directory. Running ./install.sh -u from any other location will result in a failed upgrade.

cd install
./install.sh -u

Tip

If the cluster has been intentionally stopped before the upgrade, you can bypass the index compatibility check by passing the --skip-check flag:

./install.sh -u --skip-check

Use this only when you have already verified that all cluster indices are compatible with the target version.

Upgrade to Version 8.0.0

Warning

Upgrading to 8.0.0 requires a full cluster restart. Rolling upgrades are not supported for this version. An upgraded node will not join an existing 7.x cluster.

Pre-upgrade steps

The Data Node update process will shut down the database service (logserver.service). Execute the following steps before running the upgrade:

  1. Stop the collectors (network-probe, logstash, and others):

systemctl stop logserver-probe

  1. Disable shard allocation:

curl -u $USER:$PASSWORD -X PUT "127.0.0.1:9200/_cluster/settings" \
  -H "Content-Type: application/json" -d '{
  "persistent": {
    "cluster.routing.allocation.enable": "none"
  }
}'

  1. Perform a flush:

curl -u $USER:$PASSWORD -X POST "127.0.0.1:9200/_flush?pretty"

  1. Run the upgrade:

./install.sh -u

Multi-node upgrade order

For multi-node deployments, run the upgrade in this order:

  1. Start with the client node (the node that serves the GUI and coordinates queries).

  2. When install.sh asks whether to restart services, answer No. Services on each upgraded host stay stopped until every node has finished the upgrade.

  3. Upgrade the remaining data nodes one by one using the same procedure.

  4. Once every node has completed install.sh -u, start the services manually across the cluster - logserver first on each data node, then the remaining services.

Warning

The data-node RPM stops logserver.service on the host being upgraded, so the cluster runs degraded from the first node onwards. Do not let the installer restart services mid-upgrade - restart them manually only after every node has been upgraded.

Index compatibility check

The upgrade requires reindexing for indices created in versions older than Energy Logserver 7.4.0. The installation process (./install.sh -u) performs a compatibility check automatically and outputs a list of incompatible indices. These indices must be either reindexed or deleted before the upgrade can proceed.

To check index compatibility manually before downloading the installer package:

ELS_URL="http://127.0.0.1:9200"
ELS_AUTH='user:pass'

indices_metadata="$(curl --fail -XGET --insecure -u "${ELS_AUTH}" \
  "${ELS_URL}/_cluster/state/metadata?filter_path=metadata.indices.**.index.version.created&pretty")"

mapfile -t indices_to_upgrade < <(echo "${indices_metadata}" | tr '\n' ' ' \
  | sed -e 's/ //g' \
        -e 's/,"\([^ "]\+\)":{"settings":{"index":{"version":{"created":"\([0-9]\+\)"}\+/ \1 \2/g' \
  | grep -o '\S\+ [0-9]\+' \
  | awk '$2 < 136217827 { print $1 }' \
  | sort)

printf "%s\n" "${indices_to_upgrade[@]}"

If any indices are listed, they must be reindexed or removed before upgrading.

Breaking and major changes

  • JVM options: The file jvm.options is overwritten by the upgrade. User-defined JVM settings must be placed in /etc/logserver/jvm.options.d/. Specifically:

    • Heap size settings (-Xms, -Xmx) are now in /etc/logserver/jvm.options.d/heap-size.options

    • JVM temporary directory (-Djava.io.tmpdir) is now in /etc/logserver/jvm.options.d/tmp-dir.options

    If the Data Node had additional settings in jvm.options, move them from /etc/logserver/jvm.options.rpmsave to /etc/logserver/jvm.options.d/.

    Warning

    -Djava.io.tmpdir cannot be set to a path inside /etc/, /usr/, or /boot/.

  • Java update: OpenJDK 21 is now required (previously OpenJDK 17).

  • Service names change:

    Old name

    New name

    elasticsearch

    logserver

    kibana

    logserver-gui

    logstash

    logserver-probe

    Old names still work with systemctl but journalctl requires the new names.

Post-upgrade verification

systemctl status logserver logserver-gui logserver-probe intelligence intelligence-scheduler alert license-service skimmer e-doc --no-pager

Upgrade from Version 7.9.0

Standard upgrade path with no special migration steps.

./install.sh -u

Post-upgrade verification:

  • Verify all services are running:

systemctl status logserver logserver-gui logserver-probe intelligence intelligence-scheduler alert license-service skimmer e-doc --no-pager

  • Test new features accessibility

  • Check log processing continuity

Upgrade from Version 7.8.0

Preferred Upgrade Steps for 7.8.0

  1. Run upgrade script:

./install.sh -u

Required Post Upgrade from Version 7.8.0

Breaking and major changes

  • Keystore migration: The default password store has been renamed from passstore to logserver.keystore. Run the password utility to migrate:

/usr/share/elasticsearch/utils/logserver-password-util.sh update_services --yes --no-restart --quiet

  • Java update: OpenJDK 17 is now required. The upgrade script sets the correct Java version automatically. Verify after upgrade:

java -version

  • Backup scope expanded: The configuration-backup.sh script now includes additional configuration files for license-service, intelligence, and logserver-store. Run a post-upgrade backup to capture the full scope:

bash /usr/share/elasticsearch/utils/configuration-backup.sh

Post-upgrade verification:

systemctl status logserver logserver-gui logstash intelligence intelligence-scheduler alert license-service skimmer e-doc --no-pager

Upgrade from Version 7.7.0

Standard upgrade path with minimal changes.

./install.sh -u

Post-upgrade verification:

  • Test new features accessibility

  • Verify all services functionality

  • Check log processing continuity

Upgrade from Version 7.6.0

Preferred Upgrade Steps for 7.6.0

  1. Run upgrade script:

./install.sh -u

Required Post Upgrade from Version 7.6.0

Breaking and major changes

  • Archive: Changed the default archives location to /usr/share/logserver-gui/data/archive/archives/ - please adjust external storage resource to this path [if used]. To customize the archive.archivefolderpath directive edit the /etc/logserver-gui/logserver-gui.yml file and restart the logserver-gui service.

sed -i 's|archive.archivefolderpath:.*|archive.archivefolderpath: "/usr/share/logserver-gui/data/archive/archives/"|' /etc/logserver-gui/logserver-gui.yml

systemctl restart logserver-gui

  • Network-Probe: Move required directives from /opt/license-service/license-service.conf to /opt/license-service/license-service.conf.rpmnew and replace license-service.conf then restart the license-service.

Upgrade from Version 7.5.0

Preferred Upgrade Steps for 7.5.0

  1. Run upgrade script:

./install.sh -u

Required Post Upgrade from Version 7.5.0

Breaking and major changes

  • User “logserver” will no longer be able to log into GUI. Use “admin” user instead. The update process will print the generated password for this new user. In case you have missed it you can run the following command on your main client node to recover the password:

/usr/share/elasticsearch/utils/logserver-password-util.sh get_password -u admin -q

Upgrade from Version 7.4.2 / 7.4.3

Preferred Upgrade Steps for 7.4.2 / 7.4.3

  1. Run upgrade script:

./install.sh -u

Required Post Upgrade from Version 7.4.2 / 7.4.3

Breaking and major changes

  • Network-Probe replaces Logserver-Probe: follow the steps below.

LOGSERVER-PROBE:

  • Backup /etc/logserver-probe

cp -r /etc/logserver-probe /backup/logserver-probe-7.4-backup/

  • Uninstall old version:

Warning

This command permanently removes Network Probe configuration and data. Ensure you have a backup before proceeding.

yum versionlock delete logserver-probe-oss-7.17.11-1
yum remove logserver-probe-oss
rm -rf /etc/logserver-probe /var/lib/logserver-probe /usr/share/logserver-probe

  • Install the current Input Layer from scratch using sudo ./install.sh -i - Network-Probe Section

  • Restore from backup custom pipelines to /etc/logserver-probe/conf.d/

cp /backup/logserver-probe-7.4-backup/conf.d/* /etc/logserver-probe/conf.d/

ENERGYLOGSERVER

  • ./install.sh checks indexes compatibility before upgrading. If any problems exist, please contact product support to guide you through the upgrade process.

  • Move required directives from /etc/logserver/logserver.yml to /etc/logserver/logserver.yml.rpmnew and replace logserver.yml.

mv /etc/logserver/logserver.yml /etc/logserver/logserver.yml.backup
mv /etc/logserver/logserver.yml.rpmnew /etc/logserver/logserver.yml

LOGSERVER-GUI

  • Move required directives from /etc/logserver-gui/logserver-gui.yml to /etc/logserver-gui/logserver-gui.yml.rpmnew and replace logserver-gui.yml.

mv /etc/logserver-gui/logserver-gui.yml /etc/logserver-gui/logserver-gui.yml.backup
mv /etc/logserver-gui/logserver-gui.yml.rpmnew /etc/logserver-gui/logserver-gui.yml

  • Clear browser cache on client side.

LICENSE-SERVICE

  • If required, configure logserver_connection in /opt/license-service/license-service.conf.

  • Old configuration should be in /opt/license-service/license-service.conf.rpmsave. Do not replace license-service.conf with license-service.conf.rpmsave

EMPOWERED-AI (7.4.3 only)

  • Backup .intelligence_models, .intelligence_rule_configuration indices - if needed

  • Stop services:

systemctl stop empowered-ai

  • Delete old indices:

curl -XDELETE '127.0.0.1:9200/.intelligence_rule_configuration,.intelligence_models,.intelligence_results' -u $USER:$PASSWORD

  • Start services:

systemctl start empowered-ai

Upgrade from Version 7.4.1

Preferred Upgrade Steps for 7.4.1

  1. Run upgrade script:

./install.sh -u

No additional post-upgrade steps are required for this version.

Upgrade from Version 7.4.0

Preferred Upgrade Steps for 7.4.0

  1. Run upgrade script:

./install.sh -u

No additional post-upgrade steps are required for this version.

Upgrade from Version 7.3.0

Preferred Upgrade Steps for 7.3.0

  1. Run upgrade script:

./install.sh -u

Required Post Upgrade from Version 7.3.0

ENERGYLOGSERVER

  • ./install.sh checks indexes compatibility before upgrading. If any problems exist, please contact product support to guide you through the upgrade process.

  • Move required directives from /etc/logserver/logserver.yml to /etc/logserver/logserver.yml.rpmnew and replace logserver.yml.

LOGSERVER-GUI

  • Move required directives from /etc/logserver-gui/logserver-gui.yml to /etc/logserver-gui/logserver-gui.yml.rpmnew and replace logserver-gui.yml.

  • Clear browser cache on client side.

LOGSERVER-PROBE

  • Backup /etc/logserver-probe

  • Uninstall old version:

yum versionlock delete logserver-probe-oss-7.17.11-1
yum remove logserver-probe-oss
rm -rf /etc/logserver-probe /var/lib/logserver-probe /usr/share/logserver-probe

  • Install the current Input Layer from scratch using sudo ./install.sh -i - Network-Probe Section.

  • Restore from backup custom pipelines to /etc/logserver-probe/conf.d/

LICENSE-SERVICE

  • If required, configure logserver_connection in /opt/license-service/license-service.conf.

  • Old configuration should be in /opt/license-service/license-service.conf.rpmsave. Do not replace license-service.conf with license-service.conf.rpmsave

EMPOWERED-AI Migration (7.3.0 only):

curl -X POST "localhost:9200/_snapshot/backup_repo/intelligence_backup" -H 'Content-Type: application/json' -u $USER:$PASSWORD -d'
{
  "indices": ".intelligence_models,.intelligence_rule_configuration"
}'

systemctl stop empowered-ai
yum remove empowered-ai

./install.sh -u