Version Verification and Planning

Confirm what you are running and verify the supported upgrade path before you download the installer. This page shows how to read the installed version and license, check cluster health, and plan the upgrade to Energy Logserver 8.0.

Current Version Check

The installed product version is the value you match against the Compatibility Matrix. Read it from the installed packages on the node:

rpm -qa | grep energy-logserver

Example output:

energy-logserver-data-node-8.0.0-1.x86_64
energy-logserver-client-node-8.0.0-1.x86_64
energy-logserver-siem-plan-8.0.0-1.x86_64

The version segment (8.0.0-1) is your current release.

Note

The cluster root endpoint reports the underlying OpenSearch engine version, not the Energy Logserver product version:

curl -u $USER:$PASSWORD -X GET "http://localhost:9200/"

The version.number it returns (for example 3.3.2) is the search engine build. Use the installed package version above for upgrade planning.

License and Entitlements

Review the active license before planning. The upgrade reuses the existing license file, but the license also defines the node count and add-on features you are entitled to:

curl -u $USER:$PASSWORD -X GET "http://localhost:9200/_logserver/license"

The response lists the licensed node count (nodes), expiration (expiration_date, days_left), and the enabled add-ons (siemPlan, networkProbe, and others). The version field records the release the license was issued for, which can be older than the installed build: a license issued for any release from 7.4.0 onwards stays valid on 8.0, so treat this field as entitlement information, not as the running version. A new license is only required to enable add-on features introduced in a newer release. See Licensing for details.

System Health Pre-Check

Confirm the cluster is healthy and has resource headroom before you start:

curl -u $USER:$PASSWORD "http://localhost:9200/_cluster/health?pretty"

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

df -h /usr/share/logserver /var/lib/logserver

free -h

A green or yellow cluster status, all services active, and free disk on the data path are the baseline for a safe upgrade.

Pre-Upgrade Checklist

Complete these steps before running install.sh -u:

  1. Back up the cluster. Take a full snapshot so you can roll back if the upgrade fails. See Backup and Recovery and Rollback Procedures.

  2. Check index compatibility. Indices created on versions older than 7.4.0 must be reindexed or deleted first. Run the compatibility check before you download the installer, as described in Index compatibility check.

  3. Preserve custom configuration. The upgrade overwrites jvm.options; move custom JVM settings into /etc/logserver/jvm.options.d/. Review the full list in Breaking and major changes.

  4. Verify loopback access on multi-node clusters. The installer connects to the data node at 127.0.0.1:9200. Confirm network.host in logserver.yml includes the loopback address before upgrading, as described in Multi-node upgrade order.

  5. Confirm license entitlements. Check that the active license covers the target deployment, and obtain a new license first if you plan to enable a new add-on feature.

  6. Plan the maintenance window. See Upgrade Downtime for estimates.

Capacity and Requirements

An in-place upgrade keeps the existing hardware, so no additional CPU or memory is required beyond the running deployment. Confirm the node still meets the hardware and software baseline for the target release in System Requirements.

Reserve free disk headroom on the data path for the pre-upgrade snapshot, and for any reindexing the compatibility check flags. Both consume additional space on top of the existing indices.

Compatibility Matrix

The Compatibility Matrix defines the supported upgrade paths to Energy Logserver 8.0. Match your current version, read from rpm -qa above, against the table.

Warning

Upgrading to 8.x requires a full cluster restart. Rolling upgrades are not supported, and an upgraded node will not join an existing 7.x cluster.

From Version

Direct Upgrade

Notes

7.4.0 - 7.9.x

Supported

Full cluster restart required. install.sh -u checks index compatibility; indices created on versions older than 7.4.0 must be reindexed or deleted before upgrading.

< 7.4.0

Multi-step

Requires an intermediate upgrade to a version between 7.4.0 and 7.9.0 first, then reindexing incompatible indices, then upgrading to 8.x. Alternatively: a fresh 8.x installation and data migration.

7.2.x and below

Unsupported

Complete reinstallation needed

Upgrade Downtime

Single-node deployment:

  • Downtime: approximately 1 hour

  • Process: full backup, stop services, run install.sh -u, verify

Multi-node cluster:

  • Downtime: depends on cluster size and index count; plan for an extended maintenance window

  • Process: stop all collectors, upgrade the client node first, then the data nodes one by one, answering No to the installer’s restart prompt. Start services manually only after every node has been upgraded. See Multi-node upgrade order for the full procedure.

Rolling upgrades within 7.x:

  • Downtime: 15-30 minutes

  • Process: node-by-node upgrade with service continuity, available only for upgrades within the 7.x release line. See Rolling Upgrades.