Announcement
Release Notes for 2.3.3
2009/02/24
Release Notes for Zenoss Version 2.3.3
These release notes contain important information about this release of Zenoss™, including:
What's New in This Release?
- For Enterprise customers, Zenoss now offers the WebsphereMonitor ZenPack, which comprises a basic Websphere template and zProperties for Websphere monitoring.
- The Enterprise ZenWebTx ZenPack now supports extracting data from XML documents by using xpath queries.
- For Enterprise customers, Zenoss now provides comprehensive monitoring of your VMware infrastructure. It collects performance data from VMware servers (hosts), virtual machines (guests), VMware clusters and VMware data stores. By monitoring the entire VMware stack, Zenoss provides a complete picture into VMware's performance and availability, allowing you to quickly troubleshoot VMware-related problems.
- Zenoss expands your ability to monitor Java applications with improved JMX monitoring and error reporting. Zenoss also can receive JMX events that are sent from JMX applications.
- This version of Zenoss also provides improvements to monitoring the performance and availability of Windows servers. It collects data by using Windows Management Instrumentation (WMI) and Windows Perfmon.
- Zenoss offers an expanded list of ZenPacks for download, including more than 50 community-contributed monitoring ZenPacks.
- Zenoss documentation is now licensed under the Creative Commons Attribution-Share Alike 3.0 Unported License, which allows you to copy, distribute, transmit, and adapt Zenoss documents under certain conditions. For details, go to this URL:
http://creativecommons.org/licenses/by-sa/3.0
Downloading Zenoss Version 2.3.3
Zenoss Core 2.3.3 is available from this location:
http://www.zenoss.com/download
Zenoss Enterprise 2.3.3 is available from the Zenoss download site. Contact your Zenoss representative for more information.
Supported Software and Environments
You can install Zenoss 2.3.3 on these platforms:
- Linux®
- RedHat® Enterprise 3, 4, 5
- Fedora™ Core 6, 7, 8
- Ubuntu® Server 6.06, 8.04
- openSUSE 10.2, 10.3
- SUSE® Enterprise 10
- Mac OS® X v10.5 Leopard®
- Windows® (requires VMware™ Player and the Zenoss Virtual Appliance)
To run and use Zenoss 2.3, you need:
- One or more monitored targets, such as:
- Windows server (2000, 2003, 2008), Windows XP, and Windows Vista®
- Linux or other UNIX® server
- VMware ESX host
- Tomcat™ or other Java/JMX server
- Any SNMP-enabled device
- For each system that will access Zenoss through a Web browser:
- Adobe® Flash® Player
- Firefox 2.x, Firefox 3.x, or Internet Explorer 7
Installation, Upgrade and Implementation Notes
Read this section for important installation, upgrade, and implementation updates. (For complete installation and update instructions, refer to the latest version of Zenoss Installation.)
Installation
Minimum system requirements for installing the Zenoss appliance are:
- 2GB RAM
- 20 GB free disk space
Appliance Upgrade
If you see the following error when following the "conary migrate" instruction to upgrade the Zenoss Virtual Appliance image:
group-zenoss-enterprise was not found on branch...
then insert
devel//
in the string. For example, if migrating from Zenoss Enterprise Version 2.2.x to Version 2.3.3, enter this command:
conary migrate --interactive --resolve group-zenoss-enterprise=/zenoss-project.zenoss.loc@zenoss:devel//enterprise-2.3
Upgrade Paths
Refer to the following table to determine the upgrade path you must follow when upgrading to a newer version of Zenoss.
| If your current version is: |
You can upgrade directly to this version: |
| 2.1.x |
2.1.3 |
| 2.1.3 |
2.2.4 |
| 2.2.x |
2.2.4 |
| 2.2.4 |
2.3.3 |
| 2.3.x |
2.3.3 |
Note: Zenoss strongly recommends that you upgrade to Release 2.3.3. When you upgrade to the latest software release, you receive the latest features and defect fixes.
Distributed Collector
If you have 2.3.1 or 2.3.2 distributed collectors, you must manually update them through the user interface before they will function correctly in 2.3.3.
To update distributed collectors:
- On the Navigation menu, click Collectors.
- Select the distributed collector from the list.
- Select Update Collector from the table menu.
- Click OK to update the collector.
VMware
If you have modeled VMware ESX servers by using the ZenossVirtualHostMonitor ZenPack (meaning that you have devices under /Devices/Server/Virtual Machine Host/ESX), do not model them by using the new ZenVMware ZenPack if you want the data to persist across the upgrade.
Windows Monitoring
Zenoss recommends that monitored machines running Windows 2000 be updated with the latest Microsoft patches.
Known Issues
The following issues are known for Version 2.3.3:
- If you encounter an issue with a Nagios plug-in utility (such as check_snmp) when using the stack installers, refer to the Trac ticket for a workaround. (Defect 4413)
- When modeling a Windows 2000 device for the first time, you may see the following error:
Traceback (most recent call last): File "/usr/local/zenoss/zenoss/ \
Products/ZenUtils/Driver.py", line 49, in _next self.iter.next().addBoth \
(self._finish) StopIteration
This error is benign and can be ignored. It will not appear on subsequent modeling attempts. (Defect 4416)
- Previously collected Windows performance graph data is not available after upgrading from Version 2.2.x to Version 2.3.x. (Defect 4071)
- The VMware ZenPack cannot collect performance data if the system clocks for the Zenoss installation and VMware server are not in sync.
- ZenJMX requires Sun Java SE Version 5.0 or higher to perform correctly. If you have a different version of Java, ZenJMX appears to run but is not functional.
- Error messages from one user can appear in multiple sessions. (Defect 3992)
- In Windows 2000, logical disk performance counters are disabled by default. After Zenoss models file systems for Windows 2000, it does not gather performance data until you modify the server to enable those performance counters. To enable the performance counters, use the diskperf command on the server. For more information, read the Microsoft Knowledge Base article titled "Using Diskperf on Windows 2000" at http://support.microsoft.com/kb/253251.
- When you delete a collector, its devices are left without an assigned collector. Zenoss recommends that you reassign assigned devices prior to deleting the collector.
- Log data displayed for the zenhub daemon (available from the Daemons tab for a hub) comes from the $ZENHOME/log/zenhub.log file, irrespective of whether you have configured Zenoss to direct log output to another file.
Defects Fixed in the 2.3.x Releases
The following defects were resolved in Version 2.3.3 of Zenoss.
| Ticket Number |
Description |
| 3918 |
NtpMonitor returning null value for all checks. |
| 4020 |
Renaming a device with Discovery protocol "none" results in error. |
| 4066 |
ZenRender POST calls fail when multiple collectors use the same ZenHub. |
| 4072 |
Remodel does not remove IP from interface (after IP is unbound from the interface.) |
| 4081 |
Some ZenPacks attempt to use ZENHOME as source path, disabling installation. |
| 4086 |
convToUnits raises exception if passed empty string. |
| 4101 |
ZenModeler degrades system operation when used with zenhubworker processes. |
| 4124 |
Capture and replay raw packet data for zentrap. |
| 4127 |
Cannot sort device list by IP address. |
| 4136 |
Windows service monitoring disabled in maintenance mode. |
| 4147 |
Cannot inherit from HRFileSystemMap in ZenPack modeler plugins |
| 4158 |
If zenprocess encounters device with bad community string, cycle does not complete. |
| 4161 |
zendisc does not log full network name. |
| 4165 |
When adding a device through the Web interface, hardware and operating system data
(shown on the Status tab) is not populated. |
| 4166 |
Google maps are geocoded with each reload (does not save its cache). |
| 4183 |
SNMPv1 traps improperly decoded. |
| 4192 |
Windows services monitored when Winservice Monitor = false. |
| 4214 |
Some SNMP traps cannot be captured by zentrap. |
| 4219 |
Index data is stripped from SNMP trail details. |
| 4268 |
zTelnet properties missing from CommandPlugin. |
| 4276 |
zeneventlog and zenwin not functional unless a WMI collector plugin is assigned to the device. |
| 4300 |
Remove default watchdog for zenwin and zeneventlog. |
| 4303 |
Thresholds fail when object contains property named "name." |
| 4304 |
zHardDiskMapMatch property not included in Zenoss installation. |
| 4305 |
ssIORawSent and ssIORawReceived data points set to GAUGE (rather than COUNTER). |
| 4309 |
Thresholds on COUNTER and DERIVE data points respond slowly and are inaccurate. |
| 4311 |
InterfaceMap fails when a device has interfaces with no ifType. |
| 4314 |
SNMP/WMI hybrid modeling causes ConflictError when zenhubworkers is set to 2 or more. |
| 4327 |
Availability report fails when a value is entered into the Component field. |
| 4337 |
zenpatch does not work correctly with existing changesets. |
| 4347 |
zenjmx fails if port 11111 is in use by another process. |
| 4364 |
zenhub daemon does not pass the logseverity option to zenhubworkers. |
| 4374 |
zensendevent does not allow specification of eventKey. |
| 4375 |
Disable jmxremote.port in ZenJMX by default. |
| 4376 |
Cannot edit a custom defined report that contains an error. |
| 4382 |
SNMP test commands do not show the command being used to verify the operation being tested. |
| 4385 |
Trace the results returned from performance collecting. |
| 4386 |
If file system utilization information is being collected with perform, unknown values appear for free/used/% on the OS tab of the device, for all file systems. |
| 4416 |
First model of Windows 2000 endpoint results in error. |
| 4445 |
MySQLMonitor ZenPack generates traceback on installation. |
| 4449 |
OS X installation welcome panel shows "evaluation version." |
| 4468 |
Stack installation issue on openSUSE 11.1. |
The following defects were resolved in Version 2.3.2 of Zenoss.
| Ticket Number |
Description |
| 3955 |
Add better error handling to zenpatch. |
| 3965 |
SNMP v1 traps have a 0 (zero) inserted into them. |
| 3997 |
zenping needs to reload its config if it defers loading its config. |
| 4010 |
DifferentiateTemplates migrate step skips templates with a targetPythonClass set. |
| 4014 |
Listen IP address should be configurable for zensyslog and zentrap. |
| 4023 |
A traceback error is generated when a Linux device is modeled under the /Server/Cmd class. |
| 4027 |
Logic to update pickle files is flawed, leading to outdated information read by zenperfsnmp on start. |
| 4031 |
Missing init .py files for Modelers. |
| 4032 |
The zenrender daemon does not send heartbeats. |
| 4033 |
Do not allow creation of a user named "user." |
| 4048 |
User interface implies monitoring of UDP services is possible. |
| 4069 |
zenpop3 fails when using SSL. |
| 4070 |
Legend on threshold graph points is imprecise. |
| 4092 |
Event console doesn't update. |
| 4100 |
zenmodeler collects all devices (rather than the single device assigned to the collector). |
| 4110 |
Alert message must use field in body to appear in clear body. |
| 4111 |
Some vendors require that a .0 be inserted between the enterprise and specific OIDs in V1 traps. |
To view the list of defects fixed in Version 2.3.1, click this link:
http://tinyurl.com/5mxtbs
To view the list of defects fixed in Version 2.3.0, click this link:
http://tinyurl.com/6ecgkn
Documentation Corrections and Updates
This section includes release-related documentation changes and corrections that do not appear in the product documentation.
Zenoss Installation for Core Version 2.3
In the chapter titled "Chapter 1. Installing Zenoss from the Stack Installers," Step 1 is changed to:
- Download the Zenoss installation files from the suse/ directory at http://support.zenoss.com/download.
Zenoss Administration for Version 2.3
The following section has been added for the WebsphereMonitor ZenPack:
The WebsphereMonitor ZenPack (available to Zenoss Enterprise customers) consists of a basic Websphere template and zProperties for Websphere monitoring.
The Websphere ZenPack depends on the latest version of the ZenWebTx ZenPack (Version 2.5).
You must have the Performance Monitoring Infrastructure (PMI) servlet installed and enabled on your Websphere instance to successfully monitor Websphere with this ZenPack.
The Websphere ZenPack includes these zProperties:
- zWebsphereURLPath - Path to the PMI servlet on a Websphere instance. The default value is the default path on a Websphere installation: wasPerTool/servlet/perfservlet.
- zWebsphereUser - Used for HTTP basic authentication. This field is not required, and is empty by default.
- zWebspherePassword - Used for HTTP basic authentication. This field is not required, and is empty by default.
- zWebsphereAuthRealm - Used for HTTP basic authentication. This field is not required, and is empty by default.
- zWebsphereServer - Used by the provided template to build the xpath queries for the data to collect. You must supply a value for this field. There is no default value.
- zWebsphereNode - Used by the provided template to build the xpath queries for the data to collect. You must supply a value for this field. There is no default value.
Reporting Problems and Providing Feedback
Use the Zenoss forums and Trac to submit issues and provide feedback.
If you are a Zenoss Enterprise customer, you also can contact your Zenoss representative.
Documentation Feedback
Zenoss welcomes your comments and suggestions to help us improve our documentation. Please send your comments to: docs@zenoss.com.
