Well, I've upgraded Zenoss using RPM again on CentOS 4.5.  Once again the
data migration failed (seems to always happen somewhere).  I managed to get
it to complete, finally.  I still have some issues.

The Google Maps are still taking so long as to be unusable.  They don't peg
the CPU as bad, but just take entirely too long to render (minutes).  This
could possibly be related to the problem further down.

Some of the new screens look very good, however a couple of things that I
don't like about the new interface.  It no longer gives any indication of
the number of events that have been acknowledged.  I liked in the old
interface where if everything was acknowledged the presentation was dimmed
(and it showed both total and acknowledged).  The device organizers no
longer provide any type of detail on the devices, only the pill of events.
It used to be that I could bring up the class/group/location and see what
hosts were in Maintenance (intentional or not) and the events.  Now in order
to see the mode I have to either go into each device, or dig down in to the
reports.  Inconvenient.

The major problem I have now is I can't pull up any of the individual
devices.  Every time I try, I get:
Type: TypeError
Value: unhashable type

Traceback (innermost last):
...
    * URL: file:ZenModel/skins/zenmodel/deviceStatus.pt
      Line 76, Column 12
      Expression: standard:'here/getDeviceComponentEventSummary'
      Names:

      {'container': <ZentinelPortal at /zport>,
       'context': <Device at /zport/dmd/Devices/Server/Linux/devices/dns01>,
       'default': <Products.PageTemplates.TALES.Default instance at
0xb7706f8c>,
       'here': <Device at /zport/dmd/Devices/Server/Linux/devices/dns01>,
       'loop': <Products.PageTemplates.TALES.SafeMapping object at
0xb32ee44c>,
       'modules': <Products.PageTemplates.ZRPythonExpr._SecureModuleImporter
instance at 0xb7719eac>,
       'nothing': None,
       'options': {'args': ()},
       'repeat': <Products.PageTemplates.TALES.SafeMapping object at
0xb32ee44c>,
       'request': <HTTPRequest,
URL=http://nmc02:8101/zport/dmd/Devices/Server/Linux/devices/dns01>,
       'root': <Application at >,
       'template': <FSPageTemplate at /zport/deviceStatus used for
/zport/dmd/Devices/Server/Linux/devices/dns01>,
       'traverse_subpath': [],
       'user': tdavis}

    * Module Products.PageTemplates.Expressions, line 185, in __call__
    * Module Products.PageTemplates.Expressions, line 180, in _eval
    * Module Products.PageTemplates.Expressions, line 85, in render
    * Module Products.ZenModel.Device, line 1539, in
getDeviceComponentEventSummary
    * Module Products.ZenEvents.EventManagerBase, line 629, in
getDeviceComponentEventSummary
    * Module sets, line 429, in __init__
    * Module sets, line 374, in _update

TypeError: unhashable type

The last time I tried to do a zendump, that failed too.  Unfortunately,
since it's using ZoDB it's not as easy to manipulate and extract the data as
it would be were it in MySQL.  Anyone have any ideas how I can clean up this
data (without having to start over and load 150 devices + templates)?


_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to