Considerations and workarounds
Excessive zeneventd memory usage
0 0 * * * /usr/bin/serviced service restart zeneventd >/dev/null 2>&1
Maintenance windows now process devices in batches of 200
(ZEN-28886) The zenactiond.conf file now has a setting for batches to process devices for maintenance windows in groups of 200. Previously, batching was not enabled. To change the default batching, edit the following line in the zenactiond.conf file in Control Center:
All timestamps now use local time zone
(ZEN-28883) Previous releases used a mixture of timestamps throughout Resource Manager (UTC and local time zone). For ease and consistency, all timestamps now use the local time zone.
Removing support for Internet Explorer 10
(ZEN-27386) Starting with Resource Manager 6.0.0, Internet Explorer 10 is no longer a supported browser.
Compatibility with Zenoss Service Impact
This version of Resource Manager is compatible with Zenoss Service Impact version 5.2.2 or later. If you use Zenoss Service Impact and upgrade to or install Resource Manager 6.0.0, you must also upgrade to or install Zenoss Service Impact 5.2.2 or later.
NFS client 4.1 is not supported
A file locking defect might exist in NFS 4.1 with RHEL/CentOS 7.4, which could cause zeneventserver to crash and other DFS-related problems. For more information, refer to topic "Configuring NFS 4.0" in the Control Center installation guide or upgrade guide, or knowledge base article Potential Issues Running With RHEL 7.4 Or CentOS 7.4.
CentralQuery maximum memory allocation pool
(ZEN-15907) The size of the CentralQuery maximum memory allocation pool is set by the RAMCommitment variable in the CentralQuery service definition. The default value is 1024MB. Do not change the value to anything less than 1024MB.
Loading MIBs change
- If the OID exists in the same MIB module, it overwrites the OID with data from the source.
- If the OID exists in a different MIB module, it deletes the OID, and then creates the OID as defined in the source.
- If the OID does not exist, it creates the OID as defined in the source.
- With the implementation of Solr indexing, during an upgrade, two migrations automatically run; the Solr index is built, and the production state migrates to Solr. This process might take several hours, depending on the size of your system.
- If you are using the following ZenPacks, you must manually update
them after upgrading to Resource Manager 6.0.0: