Page History

...

...

If you are running an earlier version of Uptime Infrastructure Monitor, please refer to Upgrading to Uptime Infrastructure Monitor 7.1 or Earlier and complete your upgrade to Uptime Infrastructure Monitor 7.1 before proceeding.

Version-Specific Upgrade Advisories

...

1. Download the Installer file from the Uptime Infrastructure Monitor 7.6 Monitoring Station Installer Files (includes up.time Controller) section of the Support site. The current names of the Uptime Infrastructure Monitor Installer files are listed below 

   Note

   Icon

   On earlier Uptime Infrastructure Monitor versions, there were separate installers for Red Hat & SUSE, as well as separate packages for upgrading vs. a full installation. Going forth is now a single installer that covers both versions of Linux, as well both upgrades and full installs.

   Uptime Infrastructure Monitor Version	Platform & Installer Files
   7.65	Windows: up.time-7.65.0-windows.exe Linux: up.time-7.65.0-linux.bin

2. Copy the Installer file to your Monitoring Station. If using FTP, ensure you use binary mode.
3. Review the version release notes for any specific upgrade instructions.
4. Back up your current Uptime Infrastructure Monitor deployment. We recommend at least the following steps, which will back up the configuration information but not the historical performance data. Please review Backing up and Recovering Uptime Infrastructure Monitor for additional backup suggestions.
   • Generate a Problem Report with full configuration data.
     1. From within the Uptime Infrastructure Monitor web gui, navigate to the Config tab & select ‘Problem Reporting’ from the left side menu
     2. Make sure the box for “Include configuration and service monitor status history for the past” is checked.
     3. Change the default option of 3 months of configuration data to 120 months.
     4. Click ‘Generate Report’ and wait for the Problem Report to complete
     5. Download and make a copy of the resulting .zip file somewhere other than the Monitoring Station.
   • The problem report will make a copy of all the various config files & configuration data used by Uptime Infrastructure Monitor. But you should also make a back-up of the following files/directories as these maybe overwritten during the upgrade process
     • Any Scripts/Plugin Monitors configured on the Monitoring Station. Typically located in subdirectories in the <uptime_dir>/scripts/ directory. (i.e. <uptime_dir>/scripts/MonitorLogScanner etc etc)
     • Any custom Dashboards downloaded from ‘The Grid’ typically located as sub-directories in the <uptime_dir>/GUI/ directory. (i.e. <uptime_dir>/GUI/mobile or <uptime_dir>/GUI/world_map etc)
     • If you made any customization's to the <uptime_dir>/logging.conf, this will needed to be backed up, as this file has been revised in the new release.

   Note

   Icon

   To guarantee full retention of historical performance data, perform a full database backup prior to upgrading using one of the options from the Knowledge Base article Backing up and Recovering Uptime Infrastructure Monitor.
5. Log out of the Uptime Infrastructure Monitor User Interface before proceeding with the upgrade. Note that if this step is not followed, you may receive a Database is Not Responding error when attempting to restart Uptime Infrastructure Monitor after the upgrade.
6. Stop the Uptime Infrastructure Monitor services before executing the Installer: Starting (or restarting) and Stopping Uptime Infrastructure Monitor.
7. If you've previously installed the separate "up.time Controller" while running Uptime Infrastructure Monitor 7.1, you will need to manually un-install this before proceeding as the up.time Controller is now integrated into Uptime Infrastructure Monitor 7.2 and later Installer packages.
   Uninstalling the up.time Controller on Windows:
   1. Open the Programs and Features Control Panel
   2. Select the up.time Controller.
   3. Click Uninstall.
   4. Follow the on-screen prompts.

   Uninstalling the up.time Controller on Linux:

   1. Navigate to the /controller/uninstaller directory ( The default Uptime Infrastructure Monitor install directory is /usr/local/uptime/ )
   2. Run the uninstaller.sh shell script.
8. Continue to apply the Uptime Infrastructure Monitor upgrade.

   • For Linux installations, run the following commands.

     Note
     title Note
     On earlier Uptime Infrastructure Monitor versions, there were separate installers for Redhat & SUSE, as well as separate packages for upgrading vs. a full installation. Going forth is now a single installer that covers both versions of Linux, as well both upgrades and full installs.

     Code Block
     language text
     # cd /to/your/upgrade/file/path # chmod +x up.time-7.5.0-linux.bin  # ./up.time-7.5.0-linux.bin

      

     Follow the directions presented during the upgrade script.

   • Windows installations; Right click on the installer, and click on 'Run As Administrator', this will ensure that the installer runs as a local administrator account and has the permissions needed.
9. Depending on your specific environment you may need to re-apply certain changes to the config files that were backed up as part of Step #4. Do not directly re-apply the backed up copies though, as there are various changes to these config files between versions. If you are unsure of what changes to do after the upgrade, please contact Uptime Infrastructure Monitor Support directly, and provide the PR taken before the upgrade.
10. If any custom files have been removed, copy them back to their respective folders (e.g. plug-in monitors reside in the uptime scripts folder). Do not overwrite any files that already exist within the scripts directory after the upgrade. Because like the config files, there are intended changes to these files between Uptime Infrastructure Monitor versions. If you are unsure of what scripts to re-apply after the upgrade, please contact Uptime Infrastructure Monitor Support directly, and provide of the PR taken before the upgrade.  (ex. SSL lines in httpd.conf will need to be readded after an upgrade.)
11. If your Uptime Infrastructure Monitor deployment includes a UI instance, please review the additional steps required for Gadgets/Dashboards to work correctly across both instances as outlined in the Release Notes here.

...