Release Notes for Zenoss Core Version 3.0.1

This work is licensed under a Creative Commons Attribution Share Alike 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/; 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 Amazon.com, 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-072010-3.0-v02

1. About These Notes

1.1. What's New in Zenoss 3.0?

1.2. Downloading Zenoss Core

1.3. Supported Software and Environments

1.4. Installation, Upgrade and Implementation Notes

1.4.1. Memory Requirements
1.4.2. Upgrade
1.4.3. Slow Loading of Trees
1.4.4. Search

1.5. Usage Notes

1.6. Known Issues

1.7. Defects Fixed in this Release

1.8. Reporting Problems and Providing Feedback

1.8.1. Product Documentation Feedback

#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 in Zenoss 3.0?

Version 3.0 of Zenoss Core offers:

Completely redesigned user interface designed to improve operational effectiveness through simplified navigation, redesigned pages, and embedded tooltips and page tips.
Expanded integration and customization through new REST API. In addition to its scriptable command line interface, interactive shell, and expansive Web services API based on XML-RPC, Zenoss now offers a REST API with easily consumable XML or JSON return formats. The benefit to end users is more flexible and simplified options for customization and rapid integration with other management tools.
New search facility (accessed from the Infrastructure page) allows simultaneous substring search on device names, IP addresses, and device classes.
Product documentation in EPUB e-book format. You can read EPUB books from your iPhone, iPad, Sony Reader, or Nook, or by using e-reader software such as Stanza, FBReader (for Linux devices), or the EPUBReader plugin (for Firefox users).
Upgraded versions of Python (2.6) and Zope (2.12).
Reliability and availability improvements.

#1.2. Downloading Zenoss Core

Zenoss Core is available from this location:

http://www.zenoss.com/download

#1.3. Supported Software and Environments

You can install Zenoss Core on these platforms:

Linux®
- RedHat® Enterprise Linux 4, 5
- CentOS 4, 5
- Fedora^TM Core 12, 13
- Debian® 5
- Ubuntu® Server 6.06, 10.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 VMware^TM 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, 8
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®, Windows 7
Linux or other UNIX® server
Tomcat^TM 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 the Zenoss Core Installation guide.

#1.4.1. Memory Requirements

For a small Zenoss installation (fewer than 250 devices), your system must have a minimum of 4GB available RAM. (Defect 6898)

#1.4.2. Upgrade

Refer to the following table to determine the upgrade path you must follow when upgrading to a newer version of Zenoss.
Note
Zenoss strongly recommends that you upgrade to the latest release to receive the latest features and defect fixes.
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.4.5
2.4.x 2.5.2
2.5.x 3.0.1
3.0.0 3.0.1
Before upgrading from Version 2.5.x to Version 3.0.1, you must install the PreUpgrade ZenPack to prepare your environment for the transition. This version depends on a new global catalog that indexes most objects in your database for quick retrieval.
Run this ZenPack only against the #Zenoss master; do not run it against #Zenoss collectors.
To prepare your environment:
1. Download and save the PreUpgrade30 ZenPack .egg file from the Zenoss Community ZenPacks page:
  community/zenpacks
2. Run the following command as the zenoss user:
```
zenpack --install ZenPacks.zenoss.PreUpgrade30
```
3. Stop, and then restart the system with the following commands:
```
zopectl stop
zenhub stop
zopectl start
zenhub start
```
4. Run the following command to build the catalog:
```
zencatalog start
```
  When the zencatalog daemon starts, it will traverse your database and build the catalog.
  You can check the progress of the daemon from the event console, or from the zencatalog.log file. Run the following command:
```
tail -f $ZENHOME/log/zencatalog.log
```
  Note
  You must wait until zencatalog finishes before continuing upgrade. The amount of time required to create the global catalog depends on the number of devices and components in your database.
Before upgrade, you must perform a "service zenoss start" (as root user) or "zenoss start" (as user zenoss) before restarting Zenoss. (Defect 7033)
Otherwise, you will see the following error:
Daemon: zeoctl Error: no program specified; use -p or -C
Zenoss does not test or evaluate community, customer-developed, and custom ZenPacks for upgrades.
If you are using one or more ZenPacks that are not installed through the standard Zenoss installation process, you should contact the ZenPack author about its compatibility with your upgrade version. Zenoss further recommends you test the ZenPack for upgrade compatibility in a test environment.
Older versions of Zenoss used a persistent disk cache in the zope.conf file. If you originally installed an older Zenoss version, it is possible that your upgraded system still has this cache enabled. This configuration is not compatible with Zenoss 3.0.x, and must be disabled before starting the upgrade process. (Defect 7069)
Follow these steps to disable and remove the cache:
1. In the zope.conf file, verify that the client zeo1 line is commented out, as follows:
```
<zodb_db main>
  mount-point /
  # ZODB cache, in number of objects
  cache-size 5000
  <zeoclient>
    server localhost:8100
    storage 1
    name zeostorage
    var $INSTANCE/var
    # ZEO client cache, in bytes
    cache-size 20MB
    # Uncomment to have a persistent disk cache
    #client zeo1
  </zeoclient>
</zodb_db>
```
2. As the zenoss user, enter these commands to remove old caches, if they exist:
```
zenoss stop
rm $ZENHOME/var/*.zec
zenoss start
```
There is a known issue when upgrading from Zenoss 2.5.2 to Zenoss 3.0.x, for users who have installed ZenPacks with compiled C extensions. (LDAPAuthenticator ZenPacks users will most commonly experience this problem.)
The problem results from moving from Python 2.4 to Python 2.5 or later. Zenoss 3.0.x uses Python 2.6.
During upgrade, on a 64-bit OS, you may see this error during the post-upgrade process:
undefined symbol: Py_InitModule4
This message interrupts the upgrade. If it appears, you must:
1. Upgrade ZenPacks with new Python 2.6-compiled extensions
2. Run the post-upgrade cleanup script:
  remove_preupgrade_zenpack.sh
  Note
  For Enterprise ZenPacks, the post-upgrade cleanup step is included in the Enterprise ZenPack RPM installation. If you have additional custom or community ZenPacks exhibiting this error, then you must run this script manually after installing ZenPacks with new Python 2.6-compatible extensions.
  Note
  The zeo database daemon must be running when you run the script.
Users on a 32-bit OS may see this message during the post-upgrade step:
RuntimeWarning: Python C API version mismatch for module XXXX: This Python has API version 1013 module XXXX has version 1012.
where XXXX contains the name of a specific, compiled C extension. This warning will not prevent the remove_preupgrade_zenpack.sh script from completing, but it does indicate that one or more extensions must be rebuilt for Python 2.6 before you can fully deploy your updated Zenoss system.
A known issue in Zenoss Version 2.5.2 (fixed in 3.0.1) prevents proper restoration of event data. (Defect 6914)
In the unlikely event that you need to restore your Zenoss Version 2.5.2 instance from a prior zenbackup, you must patch zenrestore before restoring your instance.
As the zenoss user, enter the following command:
```
zenpatch 20751
```

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.4.5
2.4.x	2.5.2
2.5.x	3.0.1
3.0.0	3.0.1

#1.4.3. Slow Loading of Trees

If you are experiencing slow loading of trees (for example, device or network trees) in the user interface, then this patch will improve performance, particularly when monitoring a large number of devices. (Defect 7163)

As the zenoss user, enter the following command:

zenpatch 21878

#1.4.4. Search

Global Device Search is available as a Core ZenPack. You can download this ZenPack from:

docs/DOC-7453

#1.5. Usage Notes

When moving one or more devices in the device list (such as to a group or location, or to a new device class), you must click and drag from an "empty" part of a row, rather than from the links or indicators on that row. When you successfully select a row to move, a tooltip appears that indicates "n selected row."

Figure 1. Moving a Device

#1.6. Known Issues

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

A new attribute, monitoredStartModes, has been added to WinServices so that only Windows services that are expected to be running are actually reported as "down." Optional services that are Disabled or Manual startup are, by default, not reported as down. (Internal Defect 2248)
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)
Starting up the BitRock stack may produce ClientDisconnected errors in log files. These do not indicate a problem and should be ignored. (Defect 5508)
If your installation's $ZENHOME contains a dot (.), then Zenoss does not function correctly. (Defect 5838)
You must restart Zenoss (or restart zopectl) before you can export and download ZenPacks through the Web interface. (Defect 6906)
Zenoss displays a status of "unknown" for Windows services that are disabled or not monitored. (Defect 7028)
A known issue when working with template definitions corrupts graph definitions and prevents correct display of graph data. (Defect 7118)
If you select View and Edit from the Action menu in the Graph Definitions area for a monitoring template, and then save (Submit), the graph definition will corrupt. This corruption prevents the graph from displaying graph data and locks the monitoring template page.
To correct this problem, as the zenoss user, enter the following commands:
```
zenpatch 21609
zenmigrate
```

#1.7. Defects Fixed in this Release

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

http://tinyurl.com/29a7h5w

#1.8. Reporting Problems and Providing Feedback

Use the Zenoss forums (community/forums) and Trac (http://dev.zenoss.org/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:

docs@zenoss.com