Index


Prerequisites

Note:

Upgrading from v25.2 requires a new License Key. If you will not have internet access while performing the upgrade, then please contact Customer Service and request a manual license prior to the upgrade.
Upgrading from v25.3 \ v25.3.1 does not have this requirement.

  • A current v25.2+ installation
    • For upgrading from any earlier Statseeker versions, see Upgrade Guides
  • A current and valid, non-local backup of your existing Statseeker server, see Backup and Restoration Process for details
  • Ensure that you meet the hardware requirements, see System Requirements for details
  • If you are changing product tier with this upgrade, then you will require a new License Key, please contact Customer Service

[top]


Download Location & Files

[top]


Important Notes

EGAID Removal (Only applies when upgrading from v25.2)

Note: This issue only affects customers upgrading from Statseeker v25.2, with servers that date back to Statseeker v4.0 (2015) and earlier.

Previously, Statseeker maintained two internal entity ID references, the egaid (legacy ID) and the newer entityid. Entities created after Statseeker v4.0 (2015) had the same value set for these two IDs, but entities created earlier than this may have different values. Statseeker has removed the legacy egaid, and this may break some specific workflows that reference entities by their egaid when that ID differs from the entityid.

Potentially broken workflows:

  • Raw URLs in dashboard and report drilldowns: URLs containing an egaid in the URL parameters may be affected. This only affects users who have manually entered URLs. URLs constructed by selecting entries from dropdown-lists are not affected.
  • Custom form elements: Scheduled reports and Summary report configurations allow users to add custom form elements (see screenshots below). These custom form elements may reference an egaid.
Custom Form Elements (screenshots)

Recreating affected URLs or form elements so they reference current IDs will resolve the issue. If you aren’t sure which reports an egaid is referencing, contact Customer Service for assistance.

[top]

MAC/IP Data Reset (Only applies when upgrading from v25.2)

The upgrade process will clear the MAC/IP data history. This data will automatically begin repopulating once the upgrade process is complete.

[top]

SCS Packages

Some custom SCS scripts may be removed during the upgrade process, you will need to reinstall those SCS packages after the upgrade. To access current SCS packages relevant to your version of Statseeker, please contact Statseeker Technical Support.

[top]


Upgrade Procedure

  • Backup your existing data using Administration > Statseeker Administration > Backup/Restore
  • Ensure the backup is stored in a remote location, not locally on the existing Statseeker server
    • Note: for more information on the backup process, see Backup and Restore.
  • Log in to Statseeker as an Admin user
  • Select Console and confirm that:
    • The current installation is v25.2 or higher – version information is displayed at the bottom of the Console
    • The current user is admin, or is a user with the Admin role – current user is displayed in the top-right of the console

  • Select Administration > Statseeker Administration > Software Upgrade
  • Click Edit (upper-right)
  • Click Choose File, browse to the location of the stored Statseeker Upgrade image, select it, and click Open
  • Click Upload

A progress bar will be displayed to map the progress of the upload process.

Upgrading from 25.2: License Update

Upgrading from Statseeker v25.2 requires a new license. You will be prompted to either download a new license or upload a previously provided manual license.

If you have internet access:

  • Select Actions > Download a new License

Otherwise:

  • Contact Customer Service and request a manual license – they will provide you with a license file that you can upload to your server
  • Select Actions > Upload a new License
  • Browse to the location of the stored Statseeker License file, select it, and click Open

Once the license has been updated, a series of checks against the upgrade requirements is run.


Once the image has been uploaded, a series of checks against the upgrade requirements is run. In addition, a dry run of the upgrade process is conducted to highlight any potential impacts on your installation resulting from the upgrade.

The results of the upgrade checks are presented, and any items marked with a warning or failed icon should, prior to proceeding with the upgrade, be reviewed and addressed as needed.

Note: there is no requirement to complete the upgrade process at this point, and no changes have been applied to your existing Statseeker installation. You can take the time to review and address failed/warning items as needed and return to the upgrade when ready. If you have any questions regarding the status of any of the upgrade checklist items, please contact Statseeker Technical Support.

If the checklist presents items that require attention, you can click on the associated doc link to view details. Some of these items can be addressed prior to proceeding with the upgrade, and others advise a review of the affected element (threshold, report configuration, etc.) post-upgrade.

A complete, detailed report can be downloaded and used as a reference for these items and as a record of the changes made to affected elements as a result of the upgrade process. To download the upgrade report:

  • Click Download Report for an HTML report, or Download Report (gz) for an archived version of the same HTML report

Highlighted items in the upgrade checklist can be addressed, and the pre-upgrade check rerun as desired.

When you are ready to proceed with the upgrade:

  • Click Complete Upgrade

If any warning or failed/error items remain in the pre-upgrade checklist, a warning dialog is displayed asking you to confirm that you wish to proceed with the upgrade.

  • If you are happy to proceed, click Yes

The upgrade will now commence. During this process, the Statseeker server will be unavailable.

[top]


Post-Upgrade Checks

There are a number of checks to be performed once the upgrade process is complete:

[top]


Confirm new version

  • Return to the Console and refresh your browser to confirm that the upgrade process is complete and that you are running an updated Statseeker version.

The installed version number is displayed below the report list and filters.


[top]


Confirm License Details

  • From Administration select General > License Key

This will display your current license details.

Review those details, and if you require any changes to the feature set, tier, or entity limits (Device, Interface, and Custom Data), please contact Customer Service.

[top]


Reapply SCS Packages

Note: In some instances, the GUI will progress, indicating that the upgrade has completed, but some back-end processes may still be running. Either wait 15 mins post-upgrade before applying SCS packages or check that all upgrade processes have completed.

To confirm that the upgrade has completed:

  • Wait until after the server reboot, midway through the upgrade process
  • Access the server’s CLI (directly or via an SSH connection)
  • Run grep 99-base-done.sh /home/statseeker/base/logs/base-logd.log
  • Review the output for [DATE] [TIMESTAMP] [PROCESS_ID] 99-base-done.sh exited
    • E.g. 2024-01-31 15:15:17 94722 99-base-done.sh exited

    99-base-done.sh will run twice, once on either side of the server reboot which occurs midway through the upgrade process. We are looking for the second instance of 99-base-done.sh exited.

  • If the entry is not found, tail the log to be alerted when 99-base-done.sh is complete:
    • tail -100f /home/statseeker/base/logs/base-logd.log | grep ’99-base-done.sh’
  • Once 99-base-done.sh has exited, proceed with applying SCS packages


The pre-upgrade check will have highlighted any potential impacts on existing Statseeker Custom Script (SCS) packages.

  • Review your installed SCS packages after the upgrade and reapply as required

[top]

Apply Service Packs

Note: In some instances, the GUI progress will imply that the upgrade has completed, but some back-end processes may still be running. Either wait 15 mins post-upgrade before applying Service Packs or check that all upgrade processes have completed.

To confirm that the upgrade has completed:

  • Wait until after the server reboot, midway through the upgrade process
  • Access the server’s CLI (directly or via an SSH connection)
  • Run grep 99-base-done.sh /home/statseeker/base/logs/base-logd.log
  • Review the output for [DATE] [TIMESTAMP] [PROCESS_ID] 99-base-done.sh exited
    • E.g. 2024-01-31 15:15:17 94722 99-base-done.sh exited

    99-base-done.sh will run twice, once on either side of the server reboot which occurs midway through the upgrade process. We are looking for the second instance of 99-base-done.sh exited.

  • If the entry is not found, tail the log to be alerted when 99-base-done.sh is complete:
    • tail -100f /home/statseeker/base/logs/base-logd.log | grep ’99-base-done.sh’
  • Once 99-base-done.sh has exited, proceed with applying SCS packages


There are currently no service packs for Statseeker v26.3.

[top]

Backup Your Upgraded Server

Backup files from earlier versions may not have the required data structure to work correctly with your updated Statseeker server. Once an upgrade has been completed, it is strongly advised that a backup be created.

See Backup and Restoration Process for details.

[top]