This Release Notes document describes changes to the 7.9 release. For more information about the fixed issues in this release, see Resolved Issues at the end of this topic. |
Uptime Infrastructure Monitor 7.9 includes the following new and improved features.
With this release, Uptime Infrastructure Monitor 7.9 improves encryption for increased security and includes a new utility to update configuration of the Uptime data storage.
Uptime Infrastructure Monitor 7.9 updates web services to the following new versions:
This version of Uptime Infrastructure Monitor includes support for vCenter 7.0.
Users who have a bundled MySQL database cannot upgrade directly from Uptime Infrastructure Monitor 7.7.3 (MySQL 5.5) to Uptime 7.8.6 or later (MySQL 8.0). You first must upgrade to Uptime 7.8.5 before continuing on to the Uptime 7.8.6 or later upgrade. |
If you are running Uptime 7.8.6 with SUSE 12.3, you first must upgrade to SUSE 15.3 before upgrading to Uptime 7.9. |
Make sure you have enough space before attempting to upgrade to Uptime Infrastructure Monitor 7.9.x. You should have at least 40% free space before beginning the upgrade. |
The Uptime Infrastructure Monitor 7.9.x data collector includes a maxpermgen size of 160. This is up from 128 MB in Uptime Infrastructure Monitor 7.7 and earlier. Users who require custom or higher settings can reference the old config file stored at c:\uptime\config-backup\[prior uptime version]\uptime (Windows) or uptime/config-backup/[prior uptime version]/uptime/uptime.jcnf (Linux) and restore the settings after the upgrade. A data collector restart is required. Otherwise the customizations may be lost.
Upgrading the Uptime Monitoring Station will upgrade Apache, PHP, and OpenSSL. This will overwrite the Apache configuration and PHP configuration files. For users who have modified the uptime\apache\conf\httpd.conf or uptime\apache\php\php.ini, the old files will be available in the uptime\config-backup\[old uptime version]\apache\conf and php folders. When the upgrade is complete, customizations can be copied over to the new files. There are several changes in these new configuration files so please do not simply overwrite the file.
The WebLogic Service Monitor is updated to support SSL in Uptime Infrastructure Monitor 7.8.x and later. Also, email round trip service monitors using or any other service using self-signed certificates manually added to the trusted store will be overwritten upon upgrade and must be reinstalled after the upgrade is complete. For more information about this process, see the Application Monitors section about WebLogic. Because this is a pain, and you may not be aware this was ever done, it is a good idea to back it up and restore it after an upgrade. Simply back up the uptime/jre/lib/security/cacerts file prior to upgrade. Post upgrade, shut down the Uptime Data Collector (uptime core service in Linux) and Uptime Controller (Win and Linux) services, copy your old cacerts file back into that folder, and start the service up again.
Users upgrading to Uptime Infrastructure Monitor 7.9.x who previously upgraded to Uptime 7.7.x from an earlier version should back up their MySQL my.ini file before upgrading, make the following change, and then replace the newly-installed my.ini file with the backup after completing the upgrade.
To back up your MySQL.ini file
You can only upgrade directly to Uptime Infrastructure Monitor 7.9.x if your currently installed version is version 7.8.6. Users on version 7.1 must upgrade to version 7.3, then 7.5 before upgrading to 7.7.3, then 7.8.6, and finally 7.9.x. Upgrades are possible across only two minor releases. Users who are running version 6.0 or 6.0.1 must upgrade to 7.0 > 7.1 > 7.3 > 7.5 > 7.7.3 > 7.8.6 > 7.9.x. For more information, see Upgrading to Uptime Infrastructure Monitor 7.6 and later.
Users who are running version 5.5 or earlier must upgrade to 6.0 or 6.0.1 as a starting point. (Refer to the Uptime Infrastructure Monitor Knowledge Base for specific version upgrade paths.) If you are eligible for a direct upgrade path, you can upgrade using the installer for your Monitoring Station’s operating system. The upgrade process installs new features, and does not modify or delete your existing data.
Refer to one of the following topics if your current version is older than the version required for a direct upgrade:
Users who have a clustered environment should continue using the Uptime 7.7.3 agent. A change in how the UUID is formatted in Uptime 7.8.x and later causes issues when monitoring clusters. For more information about how SQL Server cluster monitoring works in Uptime Infrastructure Monitor, see the IDERA Community article, Monitor MS-SQL Clusters and Always-On Availability Groups.
Users who manually updated Apache/PHP/OpenSSL in previous Uptime Infrastructure Monitor release using these instructions and who want to upgrade to Uptime Infrastructure Monitor 7.8.2 or later, must perform the following steps before upgrading:
uptime/conf/httpd.conf
Listen UIMHTTP
Listen [port on which you want the web server to respond]
i.e. Listen 9999
For more information about manually updating Apache/PHP/OpenSSL, see Manually Update Apache and PHP on Windows and Manually Update Apache and PHP on Linux.
Users upgrading from Uptime Infrastructure Monitor 7.8.0 to 7.8.2 or later who use MSSQL as a database backend should check their [uptime install folder]\uptime.conf and take note of the drivers used. If the sqljdbc4.jar driver is not being used, nothing needs to be done. Look for:
#To use the sqljdbc4.jar instead of the default jtds jar, uncomment the following two lines, place the jar file in the uptime/core folder and restart the collector service.
If dbDriverClass is uncommented, you should comment it out prior to running the upgrade. If you wish to continue using the MSSQL native JDBC driver, you should copy sqljdbc4.jar out of the [uptime install folder]\core folder prior to upgrading as it will get removed during the upgrade. If this task is not performed, you will notice that the upgrade program fails to reinstall the MSSQL JDBC driver and the upgrade will break.
You must download the sqljdbc4.jar driver for MSSQL (https://www.microsoft.com/en-us/download/details.aspx?id=11774 and put it in the uptime/core directory after the upgrade, uncomment the line we commented prior, and restart Uptime data collector (core in Linux) service to pick up the change.
Uptime Infrastructure Monitor 7.9 introduced the use of encrypted passwords in the uptime.conf
and uptime-controller.conf
files. In order to change the default Uptime username and password, you must first change them in the datastore (i.e. MySQL, MSSQL, or Oracle). Then use the UptimeConfigUtility tool to apply the changes to the uptime.conf
and uptime-controller.conf
files.
To use this utility
To check all options, use the help command as below:
java -jar UptimeConfigUtility.jar --help
[option] [description]
-path
Path of configuration file must be passed as a first parameter
-t
To set database type
-h
To set hostname
-prt
To set port number
-d
To set database name
-u
To set database username
-pwd
To set database password
To run
java -jar UptieConfigUtility.jar [option] [parameter_value]
For example
java -jar UptieConfigUtility.jar -path C:\uptime.conf -prt 8989 -d testDB
The Uptime Infrastructure Monitor 7.9.x upgrade process for plugins is as follows:
If you have any expiration check service monitors in your environment, please verify that they are working correctly after the upgrade is complete. If you notice an error with SSLv3 handshaking in the status output, please re-create the service monitor. |
The Uptime Infrastructure Monitor 7.9.x upgrade process is as follows: Some gadgets were adjusted for 7.8.x and later and will require your attention if you are running on an MS-SQL or ORACLE database back end.
Affected gadgets include:
For Oracle and MS-SQL users, please install the ODBC driver for your database on the Uptime monitoring station.
The following links and steps help you install the drivers.
If the database and monitoring station exist on the same machine, then drivers are already installed. Only DSN will need to be created. Also, the exact name as specified in these steps must be used for the connection or the gadgets will not work. If you wish to use a different connection name, you must edit the uptimeDB.php file accordingly. |
Edit the /etc/init.d/uptime_httpd script that starts Uptime’s apache, and then add the following lines to set some of the required environment variables. Note that this should be toward the beginning of the script and the end of the other export commands, such as export PATH , export MIBDIRS etc.
|
Restart the uptime_httpd service to pick up this change.
|
If you are having trouble with installing just the Oracle InstantClient & ODBC, the likely issue is you are missing the Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) that includes the DLL that this driver needs. Another option is to install these drivers as part of the Oracle Data Access Components which is a bundle of Oracle drivers compared to the zips mentioned above. This bundle can be found on the Oracle website at http://www.oracle.com/technetwork/database/windows/downloads/index.html
In order to use the Metric gadget gadget with a SQL Server-based Datastore, you will need to uncomment the appropriate ODBC Driver in uptime_dir/gadgets/definitions/uptime.Metricgadget/uptimeDB.php.
Windows Based monitoring stations will already have ODBC itself installed as part of Windows, and should be able to use the example provided in uptimeDB.php.
Linux based monitoring stations will require the unixODBC package to be installed. This package should include the /usr/lib64/libtdsodbc.so.0 SQL Server ODBC Driver needed for MSSQL/SQLserver. Which is also the example provided in uptimeDB.php
See Oracle ODBC Driver Linux Installation above for more details on installing unixODBC.
Visit Uptime Infrastructure Monitor's Knowledge Base for the latest comprehensive listing of currently supported monitoring station, database, and agent platforms. The following tables summarize platform support changes for Uptime Infrastructure Monitor since the previous release. The following icons are used to describe the type of support available in a version:
Supported and tested
Support added in this release
Supported but not tested
Support removed in this release
Due to limited usage, we are considering dropping support for the following platforms in a future release:
If this will cause an issue in your environment, please contact Technical Support as soon as possible. |
For an expanded list of supported monitoring station platforms, see see Supported Monitoring Station Platforms in Uptime Infrastructure Monitor.
Operating System and Version | Uptime Infrastructure Monitor | |||
---|---|---|---|---|
7.9.x | 7.8.x | 7.7 | 7.6 | |
Red Hat Enterprise Linux 5.10 | ||||
Red Hat Enterprise Linux 6.4 | ||||
Red Hat Enterprise Linux 6.5 | ||||
Red Hat Enterprise Linux 6.7 | ||||
Red Hat Enterprise Linux 7.0 | ||||
Red Hat Enterprise Linux 7.1 | ||||
Red Hat Enterprise Linux 7.2 | ||||
Red Hat Enterprise Linux 7.3 | ||||
Red Hat Enterprise Linux 7.4 | ||||
Red Hat Enterprise Linux 7.5 | ||||
Red Hat Enterprise Linux 8.0 | ||||
SUSE Linux Enterprise Server 11.3 | ||||
SUSE Linux Enterprise Server 11.4 | ||||
SUSE Linux Enterprise Server 12.0 | ||||
SUSE Linux Enterprise Server 12.1 | ||||
SUSE Linux Enterprise Server 12.3 | ||||
SUSE Linux Enterprise Server 15.3* | ||||
Windows Server 2008 R2 SP1 | ||||
Windows Server 2012 | ||||
Windows Server 2012 R2 | ||||
Windows Server 2016 | ||||
Windows Server 2019 | ||||
Windows 7 SP1 | ||||
Windows 10 |
* If you are running Uptime 7.8.6 with SUSE 12.3, you first must upgrade to SUSE 15.3 before upgrading to Uptime 7.9.
For an expanded list of supported agent platforms, see Supported Agent Platforms in Uptime Infrastructure Monitor.
Operating System and Version | Agent Version | |||
---|---|---|---|---|
7.9.x | 7.8.x | 7.7 | 7.6 | |
Windows 7 SP1 Professional and Enterprise | ||||
Windows 8 Professional and Enterprise | ||||
Windows 8.1 Professional and Enterprise | ||||
Windows 10 Professional and Enterprise | ||||
Windows Server 2008 Standard and Enterprise | ||||
Windows Server 2008 R2 Standard and Enterprise | ||||
Windows Server 2008 R2 SP1 Standard and Enterprise | ||||
Windows Server 2012 Essentials and Standard | ||||
Windows Server 2012 R2 Essentials and Standard | ||||
Windows Server 2016 Essentials and Standard |
Operating System and Version | Agent Version | |||
---|---|---|---|---|
7.9.x | 7.8.x | 7.7 | 7.6 | |
Red Hat Enterprise Linux 5.7 - 5.9 | ||||
Red Hat Enterprise Linux 5.10, 5.11 | ||||
Red Hat Enterprise Linux 6.4 | ||||
Red Hat Enterprise Linux 6.5 | ||||
Red Hat Enterprise Linux 6.6, 6.7 | ||||
Red Hat Enterprise Linux 6.8 | ||||
Red Hat Enterprise Linux 7.0, 7.1 | ||||
Red Hat Enterprise Linux 7.2 | ||||
Red Hat Enterprise Linux 7.3 | ||||
Red Hat Enterprise Linux 7.4 | ||||
SUSE Linux Server 10.3 | ||||
SUSE Linux Server 10.4 | ||||
SUSE Linux Server 11.0 | ||||
SUSE Linux Server 11.1 | ||||
SUSE Linux Server 11.2, 11.3 | ||||
SUSE Linux Server 11.4 | ||||
SUSE Linux Server 12 | ||||
SUSE Linux Server 12.1 |
Operating System and Version | Agent Version | |||
---|---|---|---|---|
7.9.x | 7.8.6 | 7.7 | 7.6 | |
Ubuntu Server 12.04 LTS | ||||
Ubuntu Server 14.04 LTS | ||||
Ubuntu Server 16.04 LTS | ||||
Ubuntu Server 17.04 LTS | ||||
Ubuntu Server 18.00 LTS | ||||
Debian 7 | ||||
Debian 8 |
Operating System and Version | Architecture | Agent Version | |
---|---|---|---|
7.9.x | 7.8.x | ||
AIX 7.1 TL3 | POWER7 | ||
AIX 7.1 TL4 | POWER7 | ||
AIX 7.2 TL0 | POWER7 | ||
AIX 7.2 TL1 | POWER8 |
Operating System and Version | Architecture | Agent Version | |
---|---|---|---|
7.9.x | 7.8.x | ||
HP-UX 11.31 (11i v3) | PA-RISC/IA64/Itanium |
Operating System and Version | Agent Version | |
---|---|---|
7.9.x | 7.8.x | |
Solaris 10 U9, U10 | ||
Solaris 11.0 | ||
Solaris 11.1 (SPARC/x86) | ||
Solaris 11.3 |
For an expanded list of supported agentless monitoring platforms, see Supported Agentless Platforms in Uptime Infrastructure Monitor.
Platform and Version | Uptime Infrastructure Monitor | |||
---|---|---|---|---|
7.9.x | 7.8.x | 7.7 | 7.6 | |
HMC v6R1.3 | ||||
HMC v7R3.x | ||||
HMC v7R7.1.0 |
Platform and Version | Uptime Infrastructure Monitor Version | ||
---|---|---|---|
7.9.x | 7.8.x | 7.7 | |
ESX / ESXi 4.1 | |||
ESXi 5.0 | |||
ESXi 5.1 | |||
ESXi 5.5 GA | |||
ESXi 5.5 U1 | |||
ESXi 5.5 U2 | |||
ESXi 5.5 U3 | |||
ESXi 6.0 GA | |||
ESXi 6.0 U1 | |||
ESXi 6.0 U2 | |||
ESXi 6.5 GA | |||
vCenter 4.0 | |||
vCenter 5.0 | |||
vCenter 5.1 | |||
vCenter 5.5 | |||
vCenter 6.0 | |||
vCenter 6.5 | |||
vCenter 7.0 |
Platform and Version | Uptime Infrastructure Monitor Version | ||
---|---|---|---|
7.9.x | 7.8.x | 7.7 | |
Windows 7 SP1 Professional and Enterprise | |||
Windows 8 Professional and Enterprise | |||
Windows 8.1 Professional and Enterprise | |||
Windows 10 Professional and Enterprise | |||
Windows Server 2008 Standard and Enterprise | |||
Windows Server 2008 R2 Standard and Enterprise | |||
Windows Server 2008 R2 SP1 Standard and Enterprise | |||
Windows Server 2012 Essentials and Standard | |||
Windows Server 2012 R2 Essentials and Standard | |||
Windows Server 2016 Essentials and Standard |
For an expanded list of supported databases, see Supported Databases in Uptime Infrastructure Monitor.
Database Type and Version | Uptime Infrastructure Monitor Version | ||
---|---|---|---|
7.9.x | 7.8.x | 7.7 | |
MySQL 5.5 64-bit (Bundled) | |||
MySQL 5.6 64-bit (Bundled) | |||
MySQL 5.7 64-bit (Bundled) | |||
MySQL 5.7.21 64-bit (Bundled) | |||
MySQL 8.0.xx 64-bit (Bundled) | |||
Oracle 11g R2 (11.2.0.4) | |||
Oracle 12c (12.1.0.2) | |||
Oracle 12c (12.2.0.1) | |||
Oracle 12c R2 (12.2.2.x) | |||
Oracle 18c | |||
Oracle 19c | |||
Microsoft SQL Server 2012 | |||
Microsoft SQL Server 2012 SP1 | |||
Microsoft SQL Server 2012 SP3 | |||
Microsoft SQL Server 2014 SP1 | |||
Microsoft SQL Server 2016 | |||
Microsoft SQL Server 2017 | |||
Microsoft SQL Server 2019 |
Uptime Infrastructure Monitor is available on the latest versions of Internet Explorer, Mozilla Firefox, Google Chrome, and Microsoft Edge. For an expanded list of supported web browsers, see Supported Browsers in Uptime Infrastructure Monitor.
Web Transaction Monitor is Java-based and does NOT work with modern browsers. Creating new monitors is disabled. This monitor works only if your UIM installation already has previously-captured Web Transaction monitor recordings. This does not affect previously-configured Web Transaction Monitors. |
The Uptime Infrastructure Monitor Support Portal provides various documents and articles that guide you through a first-time installation or upgrade.
A complete, first-time deployment of Uptime Infrastructure Monitor and its agents is a straightforward process. Refer to the Installation and Quick Start Guide for complete instructions on performing a first-time installation.
UT-18649 | Resolved an issue when enabling TLS or SSL for the SMTP Configuration option |
UT-18790 | Added support for vCenter 7.0 |
UT-18794 | Added support for PHP 8.0.7, Apache 2.4.48, OpenSSL 1.1.1k |
UT-18795 | Added support for jQuery 3.6.0 |
UT-18809 | Enhanced code for increased config file encryption |
UT-18810 | Added a utility to update the datastore |
UT-18811 | Improved encryption for increased security |
For Uptime Infrastructure Monitor 7.8.5 and later, the vcruntime140.dll must be installed prior to installing or upgrading. If the .dll is not available during the upgrade or installation process, you may receive a message that the procedure failed.
|
Users who upgrade to Uptime Infrastructure Monitor 7.8.5 and later 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 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
Linux
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:
|
A Microsoft DCOM update may cause an issue for some users. When running a WMI check, users may receive the following error on the machine being scanned by WMI:
"The server-side authentication level policy does not allow the user [username] SID ([SID]) from address 111.22.33.44 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.
The following link provides more information from Microsoft:
https://support.microsoft.com/en-us/topic/kb5004442-manage-changes-for-windows-dcom-server-security-feature-bypass-cve-2021-26414-f1400b52-c141-43d2-941e-37ed901c769c.
The lmhostid returns the value '000000000000' on some occasions. This issue results from Uptime Infrastructure Monitor expecting the primary Network Interface Card (NIC) device name of eth0. If the name is not eth0, issues can result when registering your license.
Use the following workaround to rename your current NIC device name.
If you any questions about this article or the procedure itself or any of the commands contained herein, please contact UIM Support and a member of the team can help. |
Power Linux Agents have a dependency lm_sensors.so, which is part of lm_sensors-libs package(rpm) on RHEL. If not present, you can obtain this file by running 'yum install lm_sensors-libs' on RHEL platform.
You also can download the file from https://rpmfind.net by searching for lm_sensors-libs (eg : lm_sensors-libs-3.4.0-12.fc28.ppc64.rpm).
The Citrix XenApp Monitor returns a ' (null): 0x80041010 ' error on some occasions when WMI is in use. Be sure the Citrix WMI service is enabled on the Citrix XenApp host.
Users who update from Uptime Infrastructure Monitor 7.8.0 to 7.8.3 may notice that the Uptime Agent does not appear in the Windows Control Panel. If this occurs, note that the automatic installation of the Agent did not occur and you must manually start the installation.
The CPU Utilization Ratio report highlights systems with a CPU ratio over 0.0. However, an error causes Uptime Infrastructure Monitor to highlight all CPU ratio results including values of 0.0.
When running apt-get update
and apt-get upgrade
, the following error is caused by missing LSB tags and overrides from /opt/uptime-agent/bin/upt_daemon.sh
:
insserv: warning: script 'S99uptm_daemon' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: Starting upt_daemon.sh depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting upt_daemon.sh depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting upt_daemon.sh depends on plymouth and therefore on system facility `$all' which can not be true!
To prevent compatibility issues please add the following LSB tags and override to the header of upt_daemon.sh
:
### BEGIN INIT INFO
# Provides: uptime-agent-daemon
# Required-Start: $local_fs $network
# Required-Stop: $local_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Description: Uptime Agent Deamon
### END INIT INFO
The Uptime Infrastructure Monitor Linux installer assumes Apache should be or is installed in /usr/local/apache, but it checks where Uptime is installed. This causes the user to have two different install paths for Uptime, which causes Apache to fail.
If the user does not launch Uptime Infrastructure Monitor from the installer and does not receive the Auto-Discovery Wizard upon opening the product, change the URL to:
localhost:9999/autoDiscoveryWizard.php
Note that entering only localhost:9999
does not automatically run the wizard.
When uninstalling Uptime Infrastructure Monitor, the uninstall does not automatically stop or kill the stunnel.exe
process. In order to delete the Uptime directory during uninstallation, the user first must kill the stunnel.exe
process.
Legacy code used in implementing the Wait I/O report for elements using a Windows agent is causing the report to display 0 instead of a proper value. In comparison, the same stat returned when using a Linux agent shows the correct value. This issue will be addressed in a future release.
In the Quick Snapshots for both VMware and Hyper-V, the Swap Usage vs. Swap Space sometimes displays '0 undefined.' This issue will be addressed in a future release.
IDERA employees are proud to work with our clients around the globe to deliver exceptional customer service, including sales expertise, installation help, and support services.
Brookhollow Central III
2950 North Loop Freeway West
Suite 700
Houston, Texas 770092
USA
Phone 713.523.4433
Support 713.533.5003
Fax 713.688.1924
Sales [email protected]
Support [email protected] / http://support.uptimesoftware.com
Human Resources IDERA Careers
IDERA, Inc. considers information included in this documentation to be proprietary. Your use of this information is subject to the terms and conditions of the applicable license agreement.
Save
Save
Save