Info |
---|
We're here to help! Please contact IDERA support to get assistance with your upgrade. Phone: 713.533.5003 / Email: uptime-[email protected] / Web: http://support.uptimesoftware.com |
...
Info |
---|
If you have any questions or concerns about upgrading, please contact IDERA Support. Phone: 713.533.5003 / Email: uptime-[email protected] / Web: http://support.uptimesoftware.com |
...
The Uptime Infrastructure Monitor 7.8 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 a higher setting must back up their uptime\datacollector.ini (Windows) or uptime/uptime.jcnf (Linux) before upgrading or they will lose those changes.
...
...
STEP 2: Make
...
necessary Apache configuration changes.
Upgrading the Uptime Monitoring Station will overwrite the Apache configuration file. For users who have modified the uptime\apache\conf\httpd.conf, we recommend backing up this file prior to performing an upgrade. When the upgrade is complete, customizations can be copied over to the new file or the new file can be overwritten. There are several changes in this new configuration file around timeout and acceptfilter that need to remain in place, so please do not simply overwrite the file.
STEP 3: Back up the Certificate Store.
The WebLogic Service Monitor is updated to support SSL in Uptime Infrastructure Monitor 7.8. Note that any SSL 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. To avoid this occurring, it is easiest to simply back up the uptime/jre/lib/securitycacerts file prior to upgrade. Post upgrade, shut down the data collector (core) service, copy your old cacerts file back into that folder, and start the data collector.
Anchor | ||||
---|---|---|---|---|
|
Users upgrading to Uptime Infrastructure Monitor 7.8 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.
Use the following steps:
- Stop your Uptime services.
- In uptime/mysql/my.ini, comment out table_cache=256. This must be commented out because the MySQL 5.7 version is named table_open_cache.
- Search for and, if present, comment out innodb_buffer_pool_instance. This must be commented out because the MySQL 5.7 version is named innodb_buffer_pool_instances.
- Back up uptime/mysql/my.ini.
- Run the Uptime Infrastructure Monitor 7.8 installer. Note that the upgrade of tables to the new database engine may take from minutes to several hours to complete depending on database size.
- Replace uptime/mysql/my.ini with the backed up version
Users upgrading to Uptime Infrastructure Monitor 7.8 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.
Use the following steps:
- Stop your Uptime services.
- In uptime/mysql/my.ini, comment out table_cache=256. This must be commented out because the MySQL 5.7 version is named table_open_cache.
- Search for and, if present, comment out innodb_buffer_pool_instance. This must be commented out because the MySQL 5.7 version is named innodb_buffer_pool_instances.
- Back up uptime/mysql/my.ini.
- Run the Uptime Infrastructure Monitor 7.8 installer. Note that the upgrade of tables to the new database engine may take from minutes to several hours to complete depending on database size.
- Replace uptime/mysql/my.ini with the backed up version.
STEP 3: Make necessary Apache configuration changes.
Upgrading the Uptime Monitoring Station will overwrite the Apache configuration file. For users who have modified the uptime\apache\conf\httpd.conf, we recommend backing up this file prior to performing an upgrade. When the upgrade is complete, customizations can be copied over to the new file or the new file can be overwritten. There are several changes in this new configuration file around timeout and acceptfilter that need to remain in place, so please do not simply overwrite the file.
STEP 4: Back up the Certificate Store.
...
- .
Other Upgrade Considerations
...
The Uptime Infrastructure Monitor 7.8 upgrade process is as follows: Some gadgets were adjusted for 7.8 and will require your attention if you are running on an MS-SQL or ORACLE database back end.
...
Please install the ODBC driver for your database on the Uptime Monitoring Station.
Use the following links and steps when installing the drivers:
...
and steps when installing the drivers:
Info |
---|
For MS-SQL and Oracle: If database and monitoring station are installed on the same machine, the drivers may already be installed. If this is the case, only the DSN will need to be created. Also, the exact names as specified below must be used for the connection or the gadgets will not work. |
For MS-SQL
- Download and install the Microsoft ODBC driver 11 or later using the following link:
https://www.microsoft.com/en-us/download/confirmation.aspx?id=36434 - In the gadget code, we use the data source name (DSN) you enter in this step. It is important you use this exact name.
Create a DSN named ODBC Driver for SQL Server in the Windows settings at the following path:
Control Panel > All Control Panel Items > Administrative Tools > ODBC Data Source (64-bit) > System DSN - Enter your database details when creating the DSN.
...
- Follow the steps mentioned on this article to setup the ODBC driver for Oracle on your machine:
https://tensix.com/2012/06/setting-up-an-oracle-odbc-driver-and-data-source/ - In the gadget code, we use the data source name (DSN) you enter in this step. It is important you use this exact name.
Create a DSN named ODBC Driver for Oracle in the Windows settings at the following path:
Control Panel > All Control Panel Items > Administrative Tools > ODBC Data Source (64-bit) > System DSN - Enter your database details when creating the DSN.
Info |
---|
If database and monitoring station are installed on the same machine, the drivers may already be installed. If this is the case, only the DSN will need to be created. Also, the exact name as specified above must be used for the connection or the gadgets will not work. |
Resolved Issues in 7.8 (Build 7 released 2017-02-02)
UT-17810 | Move DB driver configuration settings to properties file |
UT-17643 | Infrastructure view does not display all elements |
UT-17540 | Agent installation on Solaris Sparc not working |
UT-17517 | Auto-Discovery wizard Add button enabled without any object selection |
UT-17229 | Uptime 7.7.3 needing weekly rebooting due to unresponsive GUI |
UT-17092 | Moving to MS-SQL DataStore causes issues with some gadgets |
UT-17090 | Unable to add a network device on a fresh installation of Uptime 7.7.3 with MS-SQL database backend |
UT-17079 | Controller version displaying Uptime 7.7.2 in Uptime 7.7.3 release |
UT-17073 | User-disabled default threshold values for some monitors return in the next editing session |
UT-17065 | Disk Performance Stats unavailable when using MS-SQL DataStore |
UT-17063 | Upgrade from 7.6.1 failed with multiple errors on Oracle 11g |
UT-17050 | Resource Hot Spot report does not work with MS-SQL and Oracle datastores |
UT-16441 | Service Monitor defaults populated on edit |
UT-16440 | Linux Agent Daemon doesn't auto-start on reboot for systemd environments |
UT-16427 | SQL Server (Advanced Metrics) monitor only works with 32-bit Agent |
UT-16416 | Uptime 7.7 displays Database Unavailable error after adding network device |
UT-16392 | Alert Profile Template in Custom Format disappears upon being clicked |
UT-16372 | Allow SNMP Poller to be applied to any element type |
UT-16382 | Add link to help in Installation Size window on Linux |
UT-16368 | Proxy error on some gadgets after upgrading to Uptime 7.7 |
UT-16365 | Create and edit issues on Action Profile in Uptime 7.6.1 |
UT-16360 | Service Monitor Metrics report for ESX (Advanced Metrics) as PDF contains incorrect headers on graph |
UT-16354 | Auto-Discovery Wizard Select All Devices check box not working |
UT-16318 | Uptime not operational after installation on RHEL 7.1 or 7.2 |
UT-16315, UT-16262 | All completed Auto-Discovery Wizard fields are cleared/reset after an error message appears |
UT-16314 | Uptime hangs during monitoring due to leak of DB resources. |
UT16311 | Data Collector unavailable message includes invalid help link URL |
UT-16297 | Linux Agent on Ubuntu 14.04 psinfo error |
UT-16296 | Uptime uninstallation does not remove stunnel |
UT-16292 | Linux Agent on Ubuntu returns wrong OS version |
UT-16288 | Auto-Discovery Wizard adding vCenter before adding WMI / Agentless prevents the wizard from adding services |
UT-16265 | Auto-Discovery Wizard doesn't use all the space of an expanded window |
UT-16259 | Default Agent Service Check monitor contains no criteria for alert |
UT-16228 | Auto-Discovery Wizard finds and adds vCenter server but does not assign servers to groups or create service groups or services |
UT-16227 | Auto-discovery Wizard displays found items even with Hide Items Already Found selected |
UT-16226 | Upgrade to Uptime 7.7 from 7.6.1 is set for SNMP v2 but when you launch the Auto-Discovery Wizard the SNMP v2 checkbox is not selected by default |
UT-16225 | Auto-Discovery Back and Cancel button functionality needs clarification |
UT-16222 | Auto-Discovery Wizard doesn't stop |
UT-16221 | Create new alert profile results in long-running script |
UT-16218 | Remote Reporting functionality is blank under the Config-tab in Uptime version 7.6.1 |
UT-16207 | Allow users to specify where to put discovered VMs |
UT-16179 | Alert/Action Profiles trigger response before updating the element, causing confusing data |
UT-16178 | License Info page displays a message stating the latest version of Uptime is in use even when it is not |
UT-16177 | Edit Alert Profile dialog takes several minutes to load |
UT-16149 | Saving a dashboard with the same name but different capitalization yields an error |
UT-16160 | Values starting with a decimal point returned to Uptime Apache Status monitor get ignored |
UT-16149 | Saving Dashboard with the same name but different capitalization results in error |
UT-16145 | Network discovery fails on the Dashboard > Network link when no network devices exist |
UT-16128 | Weblogic service monitor fails when SSL is enabled |
UT-16124 | Missing agent.cfg option for Agent daemon IP restriction |
UT-16119 | Parsing metrics incorrectly showing zeros in graph and report |
UT-16111 | Agent on Linux or AIX returns incorrect number of Blocked Processes |
UT-16105 | Cannot add agent pSeries LPAR(VIO) and receive message "Error Found, hostname can't be null" |
UT-16094 | Agent installer file names need to indicate 32-bit or 64-bit and use correct Uptime spelling |
UT-16093 | Linux Agent chk4.sh grep/egrep script to find the process count incorrect |
UT-16081 | Arbitrary file upload vulnerability in post2file.php |
UT-16045 | Merge functionality of HTTP monitor, IIS Webpage plugin, and SOAP plugin |
UT-16031 | Highchart CPU Usage graph y-axis range larger than range of data points |
UT-16015 | File System Capacity Growth report displays excluded file systems |
UT-16007 | Allow user to specify which group elements are assigned when adding vCenter |
UT-15998 | Reattached service monitors cannot be detached and edited |
UT-15996 | Highchart CSS file references incorrect path name and causes graph crashes |
UT-15975 | Resource Usage report displays black outlines in the graph and scheduled report |
UT-15944 | AIX Agent should use lsps -s instead of pstat -s in perfparse.sh |
UT-15938 | Add ability to configure and schedule reports that cover only a period of time in a day |
UT-15888 | HP system displays partial info for network interfaces with names longer than 8 characters |
UT-15887 | Increase buffer return size for Web service monitor |
UT-15880 | Recreating VMs in vCenter does not successfully convert to VM+Agent when UUID is changed |
UT-15867 | ESX Hosts with Unlicensed status and licenses exceeded |
UT-15831 | Windows Element Pages In/sec always displays 0 |
UT-15827 | Issues with monitoring station support for RHEL 7.x |
UT-15814 | Index needed on ranged_object table to improve query times |
UT-15812 | Alert profile not removed from master service monitor |
UT-15800 | Adding a network device with no string value present for any index value displays an error |
UT-15613 | Improve security for Solaris, AIX, HP-UX Agents |
UT-15528 | Action Profile should not save password in plain text |
UT-15432 | SNMP poller does not retain metrics |
UT-15098 | Detach/reattach service group member monitor causes name conflict error |
PLUG-369 | Capacity Planning What-If reporting MB instead of GB on y-axis for DataStore |
PLUG-325 | SNMP Poller needs generic SNMP functionality |
PLUG-304 | Metric Chart gadget Memory graph displays negative values |
PLUG-302 | Resource Scan gadget missing from extensions.JSON |
PLUG-281 | IIS Webpage Check needs a threshold setting based on the HTTP status |
PLUG-275 | Oracle Extendable Tablespace Check plugin XML definition: Percent Free label should be Percent Used |
PLUG-277 | Move functionality from Cisco Router CPU and Memory Monitor into SNMP Poller |
PLUG-266 | FS Capacity Logical Disk doesn't recognize a single backslash in a path for exclusions |
PLUG-256 | NetApp Monitor fails immediately if SNMP is unavailable |
...
Switching to an alternative MS-SQL JDBC driver (sqljdbc4.jar) may cause the UptimeDataCollector service to crash at startup. To avoid this issue, navigate to the SQL Server property by going to Server properties > Connection > Default Connection Options > no count, and clearing the checkbox.
...
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.