Resource Manager 6.6.0
This section contains important information about release 6.6.0 of Zenoss Resource Manager (Resource Manager).
Of particular note, the option to retain performance data when re-identifying a device is deprecated.
This update includes the following performance, reliability, and usability enhancements:
- The job processing service is redesigned. For more information, see Administering job services.
- The event processing system now manages higher load and a new troubleshooting service is available, zenhubworker (user).
- Process monitoring now includes per-process memory threshold options. For more information, see Process class options.
- Embedded databases and other
enabling technologies are updated:
- MariaDB is updated to version 10.3.29.
- The RelStorage engine is updated to version 3.0.
- The Java Development Kit (JDK) is updated to version 11.
- The Python Twisted library is updated to version 20.3.0.
- The Python cryptography library is updated to 3.2.1.
- Users with the ZenOperator role can now perform basic tasks on devices and events within their assigned scope.
- The DynamicView ZenPack is updated, not deprecated as planned, and now relies on its own visualization resources. As a result, clients no longer require Adobe Flash and the zenjserver service is deprecated.
- The notification feature now supports SNMP v3 traps.
- The zentrap service now includes a configuration option to define how SNMP varbinds are handled. For more information, see Configuring varbind handling.
Considerations and workarounds
Compatibility with Zenoss Service Impact
This version of Resource Manager is compatible with Zenoss Service Impact version 5.5.3 or later. All users are strongly encouraged to upgrade Service Impact to the latest version.
Please note the following update considerations:
- Currently, the update procedures for appliance-based deployments do not include instructions for migrating the logs maintained by Control Center. (Log migration is optional.) For more information, please contact your Zenoss representative.
- Resource Manager 6.6.0 requires Control Center 1.9.0 or 1.8.0. Deployments that are not based on virtual appliances should update Control Center before updating Resource Manager.
- If necessary, preserve custom MariaDB passwords before updating. The update instructions include reminders of this requirement.
- The default handling of SNMP varbinds included in this release may not work with your existing event transforms. Please review your options before updating.
- Virtual appliance installation and update files are based on CentOS 7.9 and include Control Center 1.9.0, Service Impact 5.5.3, and Zenoss Analytics 5.1.2.
- Due to a RelStorage library update, the Resource Manager 6.6.0 update process supports only releases 6.5.0 and 6.4.1. To update earlier releases of Resource Manager to 6.6.0, first update to release 6.4.1.
- Due to the Twisted library update, the Layer2, OpenStack and OpenStackInfrastructure Zenpacks must be updated to their most recent releases before Resource Manager can be updated to release 6.6.0. Other ZenPacks that use the Twisted library may be affected, too.
- The CMDB ZenPack must be updated from version 2.1.x to version 2.2.1 (or a more recent version) before updating Resource Manager.
- The new zenjobs service may be incompatible with the installed versions of some ZenPacks. To prevent issues during updates, update ZenPacks before updating Resource Manager.
Regular expression matching limitation
(ZEN-29376) Resource Manager uses the Apache Solr search platform, which tokenizes fields. Currently, searching a tokenized field with a regex matches only a single token, limiting complex regex searches.
For example, on the INFRASTRUCTURE page, IP Address is a tokenized field. Regex search ^192.168 will not work to filter only IP addresses that start with 192.168. The Device column is untokenized; regex search on the device name works as expected.
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, see Configuring NFS 4.0 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.
(ZEN-31194) This release includes LDAPAuthenticator v3.3.3, which no longer includes an option to skip SSL certificate verification during installation or upgrade. If you are using a self-signed certificate, upload it before upgrading. For more information, see Adding an SSL certificate.
Documentation for updating high-availability deployments is not available at this time. For more information, please contact your Zenoss representative.
Device re-identification can slow or hang the system
(ZEN-32859, ZEN-31163) Re-identifying a device can cause the OpenTSDB reader service to open many connections to OpenTSDB, which in turn can slow or hang the system. This issue occurs when the re-identification is initiated through both the API and the browser interface. To prevent the issue, do not retain performance data when re-identifying devices.
On installation, the OpenTSDB database now uses 4 bytes instead of 3 bytes for the UID field. This means that
- the maximum number of data points (metric values) the database can store is now greater than 4.2 billion, up from approximately 16.7 million
- the database requires more storage space (approximately 1 byte more per stored data point)
Updates from previous releases do not get the larger field size; only new installations.
Tested operating environments
The Resource Manager application is deployed in and managed by Control Center. The operating environments of Resource Manager are the Control Center environments that are tested with a given release. The following sections identify the tested operating environments of Resource Manager and Control Center.
Resource Manager, Control Center, and operating systems
The following table identifies the tested combinations of Resource Manager, Control Center, and operating system releases.
|Resource Manager release
RHEL/CentOS 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9 (64-bit)
RHEL 8.3 (64 bit)
|RHEL/CentOS 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9 (64-bit)
|5.0, 5.1, 5.5, 6.0, 6.5
|Version 2.0 with Windows Server 2008 R2 SP1
|Version 3.0 with Windows Server 2012 and 2012 R2
Public cloud platforms
Amazon Web Services (AWS) is fully tested.
Microsoft Azure has been tested only for collector pools. Creating a full Control Center deployment to operate Resource Manager has NOT been tested on Microsoft Azure.
|Timezone localization during maintenance windows does not handle DST
|Non-zero exit codes from
zencommand breaks Nagios parsing
zencommand can generate unnecessary tracebacks
zminion service can exhaust the Redis connection limit, causing the Redis server to crash
|SNMP v3 traps are displayed as v2 traps
|Tales evaluation causes random tracebacks
|The production state of a maintenance window is set to Failed if a single device in a batch gets a conflict error
|SNMP Index information is not included in the details of SNMP devices
|Users can delete default device classes easily
collectorredis cluster does not start up correctly and Metric Shipper cannot pull metrics
zenhub "delayed calls" metric is not being collected
|Adding or searching for IP addresses or networks can fail
|Moving a device to a class with a different zPythonClass leaves out the IpAddress value
|ADM makes order-sensitive comparisons when it should not
|Zope services block when the WBEM ZenPack is installed
|ADM processing is not idempotent for all services
|SNMP traps with varbind names are not handled according to RFC conventions
|SNMP v3 modeling fails when no engine ID is returned
|Traceback events are generating with custom COMMAND ssh datasource
|Manually-defined email addresses do not get the correct timezone
|Monitoring a device stops when an event of class /Status/SNMP is received
|The ssh command does not reset connections after timeouts
|The zenhubworker (adm) service does not pick up new collectors without a restart
|The Open Events Chart portlet displays incorrect data for any arbitrary number of days that you specify
|Restarting Resource Manager leads to a spike in false positive threshold events
|SNMP collector creation fails when any event is present in /Status/Snmp
|Traceback when modelling devices manually
|Dynamic View does not change when switching between components, requires manual refresh
|Historical data is lost after re-identifying to previous device ID
|zencommand does not support a single collection run
|Event with status Down for non-pinged device (in /Status/Ping class) is suppressed
|POSKey errors not found by zodbscan and findposkeyerror
|zenmodeler traceback when a value is extremely long
This section lists ZenPacks that are automatically installed, those that are packaged but not installed, and those that are obsolete and should be uninstalled. For more information about ZenPacks, see the ZenPack catalog.
This release of Resource Manager installs the following ZenPacks at the current version listed in the table.
The following ZenPacks are packaged with Resource Manager, but not automatically installed:
ZenMailTX is obsolete. If this ZenPack is installed at your site, remove it.