2008/07/23

The latest stable packaged version of Zenoss Core, version 2.2.3 is now available for download.

Zenoss Core 2.2.3 is available from: http://www.zenoss.com/download.

This is primarily a maintenance release that addresses the following issues:

Notable Notes:

Resolving of Bad Hostnames when Upgrading Stack Installers

If you want to use a 2.2.3 stack installer (bin/rpm/deb) to upgrade an existing 2.2.0 version of Zenoss, and you are running Zenoss on a machine with a bad or incorrect hostname and you try to run zenbackup, you will get an error with stack trace.

If you correct the hostname on the machine everything will work fine. This will be fixed in future verisons of Zenoss. To track that progress you can check here.

Zenmib Directory Location for Stack Installers

When installing using a Stack Installer there is no $ZENHOME/share/mibs directory. MIBs on the stack installers are located at /usr/local/zenoss/common/share/mibs. If you are using a stack installer, make sure that you install all added mibs in the /usr/local/zenoss/common/share/mibs directory.

This will also be addressed in a future version. You can track its progress here.

Appliance Upgrade Necessary Reboot

Upon completion of an appliance upgrade from 2.1.3 to 2.2.3, you must rebooted the appliance.

Resolving of Bad Hostnames for Using ZenJMX

Zenjmx will not start successfully if the hostname of the box where the zenjmx daemon is running cannot be resolved locally. To determine if this is a problem, go to that box and run 'hostname | xargs ping'. If the ping fails, zenjmx will probably not run. To fix this, change /etc/hosts so that the boxes hostname resolves to 127.0.0.1.

Tickets and Bug Fixes

This report shows all of the fixes for Zenoss 2.2.3.

All

• 3255-    Use zendisc for adding devices
• 3378-    zenping loses login context for zencommand
• 3385-    startup script does not start watchdogs
• 3389-    adding ip to network will create the same subnet
• 3438-    daemons under watchdog control don't create pid files
• 3254-    The z-index on the message box (messageSlot) needs to be adjusted so that it displays over all other elements in IE
• 3313-    Link indexing is conceivably ambiguous
• 3352-    Backup tab fails when creating a backup
• 3404-    IE7 login fields can't be clicked on
• 3417-    Event alerts' "Event Details" link not working
• 3209-    Support setting hardware asset tag from a plugin
• 3212-    removal of old (.zip style) zenpacks does not work from the GUI
• 3213-    Add a commit() to UpdateCheck to make sure dmd.lastVersionCheckDate gets updated
• 3260-    Need to call communicate() on subprocess objects before calling wait
• 3301-    ZenPack dependencies not saving
• 3143-    zenprocess timeout errors are ugly

Appliance

• 3112-    Appliance ping on localhost (appliance itself) fails

DataCollector

• 2960-    OS Process modeling/monitoring exhibiting strange behavior
• 3294-    Allow easy specification of additional daemons for zenoss script to handle
• 3305-    Zendisc add device needs to be refactored
• 3418-    zenmodeler has very bad heartbeat handling
• 3386-    Device "Last Collection" no longer updated by zenmodeler

User Interface

• 3219-    Device edit screen no longer has collector selection drop down
• 3227-    Device Issues portlet doesn't show issues when ZenUsers look at it
• 3239-    Change logo from "Core" to "Community"
• 3252-    Network map doesn't work properly on networks
• 3274-    clicking the detail box of an event gives a javascript error "eventWindow is not defined"
• 3290-    Device List -> Delete Device gives a javascript error in firefox
• 3334-    Standard error message still has " | Core" in the logo
• 3375-    Graph refreshing is broken
• 2946-    Status "dot" for WinServices is always yellow for failed service
• 3217-    IE7: Loading the device list twice results in javascript error
• 3234-    Special characters in the geocache cause it to grow in size withoutl limit
• 3240-    "Loading" appears under logo briefly on page load
• 3250-    Command, discover and add output don't render properly in IE
• 3326-    Device/IP search box is misaligned
• 3333-    Breadcrumbs are formatted improperly on discover devices page
• 3373-    Event class mapping sequence tab crashes IE7
• 3401-    Zenoss server time no longer displays
• 2943-    orange_dot.png is too big
• 3244-    Make it somewhat easier to modify the externals in the main templates
• 3367-    Event console throws error: Class is not defined
• 3238-    New login screen    zenoss-2.2.1-verified

ZenEvents

• 3181-    EventClassKey not working properly
• 3381-    conflict error editing alerting rules
• 3413-    Events with a backslash in the component will never clear
• 3414-    Event details link from CustomEventView shows stack trace
• 2996-    Disable deletion of historical events when deleting a device

ZenHub

• 3379-    DiscoverService createDevice needs to return an indication that a device does not have auto-discover turned on

ZenJMX

• 3439-    ZenJMX doesn't compile in http://dev.zenoss.com/svn/branches/zenoss-2.2.x
• 3342-    ZenJMX doesn't close JMX connections on error
• 3411-    Add JMXMP protocol support to ZenJMX
• 3115-    Zenjmx doesn't work properly when jmx authentication is enabled.
• 3116-    Zenjmx consumes inordinate amounts of CPU
• 3325-    zenjmx heartbeat stops

ZenModel

• 3324-    Device.checkDeviceExists might fail if network root changes
• 3388-    ZenPack install/remove needs to reindex Events, Mibs and Manufacturers
• 3400-    OSProcess can't be collected by zencommand    zenoss-2.2.2-verified
• 3323-    unit test failures in mySqlEvent: device not indexed properly
• 3421-    Duplicate devices if they have different collectors
• 3297-    happierZenPackRelations migrate script needs to explicitly set parent object to be dirty
• 3436-    OperatingSystem.traceRoute doesn't respect "direct" routes

ZenPack

• 3285-    zenoss script needs to handle ZenPack-provided daemons
• 3295-    ZenJMX needs to be eggified
• 2907-    MySqlMonitor default template causes sadness for mysql versions < 5.0
• 3154-    Additional parameter to ZenPack.remove() breaks subclasses
• 3264-    Dependency checking for old-style zenpacks broken
• 3266-    ZenPackDataSourceMigrateBase does not properly index migrated datasources
• 3267-    zenpack needs to ignore dependency violation when upgrading a zenpack
• 3278-    Eggify ZenJMX    zenoss-2.2.1-verified
• 3374-    Cannot add device to Administered Objects
• 3355-    Change ApacheMonitor port parameter to a string type

ZenRRD

• 3336-    zenperfsnmp stops collecting when the hub is disconnected
• 3423-    zenrender/zenhub fails to return an error if there's no data for an RRDValue
• 3306-    zencommand doesn't send CLEAR events
• 3197-    AttributeErrors in threshold min/max values throw execptions
• 3320-    help for dealing with broken snmp agents

ZenRelations

• 3222-    RelationshipManager.oveMeBetweenRels() is doing bad things
• 3316-    importing classes from zenpacks sometimes breaks

ZenStatus

• 3149-    Possible bug in zenping discovery
• 3120-    moving or disabling ping monitoring from a device doesn't clear ping errors
• 3137-    AsyncPing.py blows up on network discovery    zenoss-2.2.1-verified

ZenUtils

• 3318-    monitor name sometimes found incorrectly
• 3335-    zenbackup fails if system's hostname is misconfigured

pynetsnmp

• 3446-    SNMP table fetch does not stop if the SNMP agent returns OIDS that don't strictly increase

zenplugins

• 3283-    Fix ZenPlugins process monitoring

zenwin

• 3233-    Support additional error handling for WMI collector plug

Enjoy!

--Zenoss Dev Team