Release Notes for Zenoss Core Version 2.5.2

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)

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.

Linux®

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

Windows® (requires VMware^TM Player and the Zenoss Virtual Appliance)

Firefox 3.x or Internet Explorer 7

Adobe® Flash® Player (for network map functionality)

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

Linux or other UNIX® server

VMware ESX Infrastructure

Tomcat^TM and other Java®/JMX servers

Any SNMP- or SSH-enabled device

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 http://support.microsoft.com/kb/253251. (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 (docs/DOC-3392), 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:

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:

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"

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/isis.py

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 = 'http://admin:zenoss@MYHOST:8080/zport/dmd/DeviceLoader'
>>> 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()