Page History

...

1. Log out of the up.time 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 up.time after the upgrade.

2. Stop the up.time services before executing the Service Pack.

   For Red Hat, SUSE, and Solaris installations, run the following:

   Code Block
   language bashtext
   # /etc/init.d/uptime_httpd stop  # /etc/init.d/uptime_core stop  # /etc/init.d/uptime_datastore stop

   For Windows installations, run the following:

   Code Block
   language vb
   > net stop "up.time Web Server"  > net stop "up.time Data Collector"  > net stop "up.time Data Store"

3. Continue to apply the up.time upgrade.

   • For Red Hat, SUSE and Solaris installations, run the following commands.

     Note that this example assumes a 7.1 Red Hat upgrade so substitute your file name as appropriate.

     Code Block
     language text
     # cd /to/your/upgrade/file/path  # gunzip -d up.time-7.1.0-rhes-upgrade.bin.gz  # chmod +x up.time-7.1.0-rhes-upgrade-bin  # ./up.time-7.1.0-rhes-upgrade.bin

     Follow the directions presented during the upgrade script.

   • Windows installations; double click on the service pack upgrade executable and follow the instructions on screen.
     
     
4. Depending on your specific environment you may need to reapply certain changes to the httpd.conf, wrapper.conf, php.ini and/or uptime.conf files. Confirm that these files are correct by comparing to your backup copies.
   
   
5. Note that after upgrading to up.time 7.0, users should update the global SNMP settings found on the Config panel (please refer to the Release Notes for further details).
   
   
6. Note that several new parameters were added or moved to the uptime.conf file in the 5.5 release to simplify and facilitate tuning of performance parameters. If these parameters were 
   previously modified in your wrapper.conf or uptime.lax file, you will need to reapply those changes to the uptime.conf file after upgrading to the 5.5 (or later) release.
   
   
7. If any custom files have been removed, copy them back to their respective folders (e.g. plug-in monitors reside in the uptime core folder). Ensure that any custom monitors, custom alerts, custom actions, or plug-in service monitors are compatible with the new service pack.