Page History

Users who upgrade to Uptime Infrastructure Monitor 7.8.5 may experience issues as a result of the Uptime version number in the Database version (viewed by clicking Help > About Uptime) not changing to the proper version number.

This issue only affects you if you run Uptime in UI-only mode where the user interface and datastore are running of on two different servers. When starting the UptimeCollector, there is a check to see whether the Uptime version is the same as the Uptime version in the database on the node with the database. When this check fails, the UptimeCollector fails to start on the UI-only node, resulting in a failure to launch the UI.

To resolve this issue, you must insert another row with the 7.8.5 Uptime version into the dbversion table with the following command on the DB node:

Windows

<UptimeInstallDir>\mysql\bin\mysql.exe -uroot -p<password> -P3308 -e "INSERT INTO uptime.dbversion (major, minor, revision, applied) VALUES(7, 8, 5, NOW())"

Linux

<UptimeInstallDir>/mysql -h 127.0.0.1 -uroot -p<password> -P3308 -D uptime -e "INSERT INTO dbversion (major, minor, revision, applied) VALUES(7, 8, 5, NOW())"

MySQL is the default database included with Uptime Infrastructure Monitor. If you are using SQL Server or Oracle, run the following command after logging into your database:

INSERT INTO dbversion (major, minor, revision, applied) VALUES(7, 8, 5, NOW())