Skip navigation
Currently Being Moderated

Release Notes for Zenoss Core Version 2.5.2

Created on: Mar 2, 2010 8:24 AM by shuckins - Last Modified:  Mar 2, 2010 4:17 PM by shuckins

Release Notes for Zenoss Core Version 2.5.2

This work is licensed under a Creative Commons Attribution Share Alike 3.0 License. To view a copy of this license, visit; or send a letter to Creative Commons, 171 2nd Street, Suite 300, San Francisco, California, 94105, USA.



The Zenoss logo is a registered trademark of Zenoss, Inc. Zenoss and Open Enterprise Management are trademarks of Zenoss, Inc. in the U.S. and other countries.

Amazon Web Services, AWS, Amazon Elastic Compute Cloud, and Amazon EC2 are trademarks of, Inc. or its affiliates in the United States and/or other countries.

Flash is a registered trademark of Adobe Systems Incorporated.

Java is a registered trademark of Sun Microsystems, Inc.

Linux is a registered trademark of Linus Torvalds.

Oracle and the Oracle logo are registered trademarks of the Oracle Corporation.

SNMP Informant is a trademark of Garth K. Williams (Informant Systems, Inc.).

Sybase is a registered trademark of Sybase, Inc.

Tomcat is a trademark of the Apache Software Foundation.

VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions.

Windows is a registered trademark of Microsoft Corporation in the United States and other countries.

All other companies and products mentioned are trademarks and property of their respective owners.


Part Number: 02-022010-2.5-v04

1. About These Notes

These release notes contain important information about this release of Zenoss, including:

  • New features

  • Where to download the software

  • Supported software and environments

  • Installation, upgrade, and implementation notes

  • Known issues

  • Defects and issues fixed in the release

  • Reporting problems and providing feedback

1.1. What's New?

Version 2.5.2 of Zenoss Core offers:

  • Improved reliability and performance, with a focus on the new event console introduced in the prior version.

  • A new Xen Virtual Hosts ZenPack for monitoring Xen para-virtualized domains and their guests.

  • More than 50 new ZenPacks (contributed by the community since Version 2.4)

Prior 2.5.x versions of Zenoss Core offer these new features and improvements:

  • A newly redesigned Event Console offers inline event filtering and improved usability. A new "Event Details" pane helps streamline troubleshooting tasks.

  • A new Community Site Window Portlet that provides easy access to Zenoss information resources.

  • The Amazon Web Services™ ZenPack, which allows you to monitor the performance and availability of Amazon Elastic Compute Cloud™ (Amazon EC2™) Web services.

Zenoss wishes to thank Ian Smith for providing the Community Site Window Portlet ZenPack, now incorporated in Zenoss.

1.2. Downloading Zenoss Core

Zenoss Core is available from this location:

1.3. Supported Software and Environments

You can install Zenoss Core on these platforms:

  • Linux®

    • RedHat® Enterprise Linux 4, 5

    • CentOS 4, 5

    • FedoraTM Core 9, 10

    • Debian® 5

    • Ubuntu® Server 6.06, 8.04

    • openSUSE 10.3, 11.1

    • SUSE® Linux Enterprise Server 10

  • Mac OS® X v10.5 Leopard®, Mac OS® X v10.6 Snow Leopard®

  • Windows® (requires VMwareTM Player and the Zenoss Virtual Appliance)

For each system that will access Zenoss through a Web browser, you need:

  • Firefox 3.x or Internet Explorer 7

  • Adobe® Flash® Player (for network map functionality)

The following partial list of resources can be managed by Zenoss:

  • Windows Server (2000, 2003, 2008), Windows XP, and Windows Vista®

  • Linux or other UNIX® server

  • VMware ESX Infrastructure

  • TomcatTM and other Java®/JMX servers

  • Any SNMP- or SSH-enabled device

1.4. 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 Core Installation.

1.4.1. Upgrade

  • 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:


    Zenoss strongly recommends that you upgrade to the latest release to receive the latest features and defect fixes.

  • If you added MIBs to your Zenoss instance, you may need to re-index them after upgrading to 2.5.2.(Defect 5895)

1.4.2. ZenPacks

Beginning with Release 2.5.0, ZenPacks in .zip format are deprecated. Refer to the section titled "Creating ZenPacks" in Zenoss Administration for instructions for creating ZenPacks in .egg format. (Defect 4350)

1.4.3. Zenplugin Support

Zenplugins are no longer supported beginning with Version 2.5.2. Equivalent functionality is available from other ZenPacks. For this instance specifically, the OpenSolaris community ZenPack is available. (Defect 6031)

1.4.4. Memory Utilization Report

The Memory Utilization performance report has been converted to use aliases. (For more information about data point aliases, see the section titled "Data Point Aliases" in the chapter Core Monitoring in Zenoss Administration.)

The following data points now have aliases.

Device ClassTemplate Data Point Alias
Server, Server/Linux, Server/Solaris, Server/CmdmemoryAvailable__bytesmemAvailRealDevice
Server, Server/Linux, Server/CmdmemoryBuffered__bytesmemBufferDevice
Server, Server/Linux, Server/CmdmemoryCached__bytesmemCachedDevice

If you have copied any of these templates, you will need to copy the aliases over manually.

1.4.5. Alternate Device Name (Title)

In Zenoss versions prior to 2.5, a single identifier ("id") was used to represent a device in the system and in the user interface. Beginning with 2.5, a separate "title" property, if specified, replaces the name of the device in the user interface. (The "id" property is the internal, unique representation of the device.) This addition accommodates situations in which a unique identifier and a "friendly" name are needed for a device. (Defect 5331)

If you have created custom reports that use the "id" property, you may want to use "titleOrId" instead, to ensure a device's title appears on the report. To change a device title, go to the device Edit tab.

To verify the device id value, view the Status page address bar. The value appears at the end of the address (for example, http://Host:8080/zport/dmd/Devices/Server/Linux/

1.4.6. Migrating MySQL Data

During the upgrade process, migrating MySQL data from may take several hours for systems with numerous events. Once started, do not stop the migration process.

1.4.7. Nagios

To enable Nagios v3 plugin output parsing, select the 'Nagios' parser. The 'Auto' parser does not support the Nagios v3 output and will generate unpredictable results. (Internal Defect 2057)

1.4.8. zenprocess

On update, you must manually delete events created by zenprocess as the deduplication field will be different for all new incoming events. The deduplication field is used to determine duplicates and to clear out events. (Defect 6000)

1.5. Known Issues

The following issues are known for this version of Zenoss Core.

  • 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 in Windows 2000" at (Internal Defect 1223)

  • Error messages from one user can appear in multiple sessions. (Defect 3992)

  • ZenPacks whose names include an underscore break on export. To resolve this issue, reinstall the ZenPack via the command line, and then restart Zope. (Defect 5239)

  • If an SSH connection times out (for example, sshd is dead, or remote device is unavailable), multiple events are generated. After SSH connections can be restored, when zencommand runs again, no clear event is generated. Events must be manually cleared when the device starts responding again. (Defect 5386)

  • COMMAND data sources now use the same component for errors and thresholds. (Defect 5394)

  • Starting up the BitRock stack may produce ClientDisconnected errors in log files. These do not indicate a problem and should be ignored. (Defect 5508)

  • When using Internet Explorer 7, after saving zProperties, the site may not appear correctly. To work around this issue, delete the 0000-00-000XX folder from the Temporary Internet Files folder. (Defect 5763)

  • When installing on OSX Server 10.6, if the /Library/LaunchDaemons directory does not exist before installation or upgrade, you must create it. (Defect 5788)

    Use the following commands:

    sudo mkdir -p /LibraryLaunchDaemons
    sudo chmod 755 /Library/LaunchDaemons
    sudo chown root:wheel /Library/LaunchDaemons
  • If you use the WMI Data Source ZenPack (, then you must upgrade to Version 1.5 before upgrading to Version 2.5.1 of Zenoss. (Otherwise, the Zenoss upgrade will not complete successfully.) Earlier versions of this ZenPack are not compatible with Zenoss 2.5x. (Defect 5794)

  • In Firefox, the event console may not correctly display all events. (Defect 5852)

    To work around this issue, follow these steps:

    1. Edit the $ZENHOME/etc/zope.conf file.

    2. Change the line that reads:

      default-zpublisher-encoding latin-1


      default-zpublisher-encoding utf-8
    3. Save and close the file.

    4. Restart Zenoss.

  • If your installation's $ZENHOME contains a dot (.), then Zenoss does not function correctly. (Defect 5838)

  • If you install two ZenPacks, and one of the ZenPacks treats the other as a namespace package, Zenoss will not function properly. (Defect 6212)

    To work around this issue:

    1. Comment out line 622 in the $ZENHOME/lib/python/zope/security/ file, which reads:

      type(pytz.UTC): NoProxy
    2. Use the zenpack --remove command to remove the ZenPack causing the issue. For example, if the ZenPacks are named "ZenPacks.zenoss.MyPack" and "ZenPacks.zenoss.MyPack.AnotherPack," remove the latter ZenPack.

    3. Uncomment line 622 in the file.

1.6. Defects Fixed in this Release

Go to the following location to view defects fixed in this version of Zenoss:

1.7. Documentation Additions

Getting Started with Zenoss

In the section titled "Setting Up WMI for Windows," Step 2 is changed as follows:

Run one of the following commands in the console to test WMI connectivity to the device:

  • If using a Windows Domain user account:

    wmic -U "DOMAIN\USER%PASSWORD" //HOST "SELECT name FROM Win32_Service"

  • If using a local Windows user account:

    wmic -U ".\USER%PASSWORD" //HOST "SELECT name FROM Win32_Service"

Zenoss Developer's Guide

  • The following information is added:

    To add a Python-ized MIB (saved from a previous run of zenmib) to the DMD, use the --evalSavedPython flag. For example:

    zenmib run -v10 --evalSavedPython=/tmp/
  • All references to wget when used against Zenoss are replaced with:

    wget --auth-no-challenge
  • Section 1.7.1, Using an XML-RPC Call from Python, is changed:

    This is an example of how to add a device using Python. Because XML-RPC can be used from any language feel free to use your favorite. What is important here is the base URL in ServerProxy, passing positional parameters, and calling loadDevice on your proxy object.

    >>> from xmlrpclib import ServerProxy
    >>> url = '
    >>> serv = ServerProxy(url)
    >>> serv.loadDevice('NEWDEVICE', '/Server/Linux')

    You can check on the device with another XML-RPC call:

    >>> from xmlrpclib import ServerProxy
    >>> cp = 'Devices/Server/Linux/devices'
    >>> url = '
    http://admin:zenoss@MYHOST:8080/zport/dmd/%s/NEWDEVICE' % cp
    >>> serv = ServerProxy(url)
    >>> print serv.getManageIp()

1.8. Reporting Problems and Providing Feedback

Use the Zenoss forums ( and Trac ( to submit issues and provide feedback.

1.8.1. Product Documentation Feedback

Zenoss welcomes your comments and suggestions to help us improve our product documentation. Please send your comments to:

Comments (0)