I had zenoss 2.2.3 running for several months. Today I upgraded to zenoss 2.3.2 
(upgraded to 2.2.4 first) and then installed ZenJMX ZenPack.

Zenjmx is not starting, I get the following messages when I run zenjmx run -v10:




Code:
DEBUG:zen.ZenJMX:run
DEBUG:zen.ZenJMX:Connecting to localhost:8789
DEBUG:zen.ZenJMX:Logging in as admin
INFO:zen.ZenJMX:Connected to ZenHub
DEBUG:zen.ZenJMX:setting up services EventService, 
ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService
DEBUG:zen.ZenJMX:chaining getInitialServices with d2
DEBUG:zen.ZenJMX:callback after getting service EventService
DEBUG:zen.ZenJMX:callback after getting service 
ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService
DEBUG:zen.ZenJMX:Calling connected.
DEBUG:zen.ZenJMX:connected
DEBUG:zen.ZenJMX:Sending event {'severity': 0, 'component': 'zenjmx', 'agent': 
'zenjmx', 'summary': 'started', 'manager': 'localhost', 'device': 'localhost', 
'eventClass': '/App/Start'}
DEBUG:zen.ZenJMX:connected(): zenjmxjavaport is 9988
DEBUG:zen.ZenJMX:connected(): cycletime is 300
INFO:zen.ZenJmxJavaClient:run():starting zenjmxjava
DEBUG:zen.ZenJmxJavaClient:run():spawn process 
('/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenJMX-3.0-py2.4.egg/ZenPacks/zenoss/ZenJMX/bin/zenjmxjava',
 'run', '--configfile', '/usr/local/zenoss/zenoss/etc/zenjmx.conf', 
'-zenjmxjavaport', '9988', '-v', '10')
DEBUG:zen.ZenJmxJavaClient:connectionMade():zenjmxjava started
DEBUG:zen.ZenJmxJavaClient:connectionMade():scheduling callback
DEBUG:zen.ZenJmxJavaClient:connectionMade(): done
DEBUG:zen.ZenJMX:connected(): launched process, waiting on callback
[2009-01-30 16:30:41,410] [INFO ] [main] 
com.zenoss.zenpacks.zenjmx.ZenJmxMain:144 - zenjmxjava configuration:
[2009-01-30 16:30:41,415] [INFO ] [main] 
com.zenoss.zenpacks.zenjmx.ZenJmxMain:145 - {hubUrl=http://localhost:8081/, 
hubUser=admin, jmxTimeOut=30, componentName=zenjmx, zenjmxjavaport=9988, 
confName=localhost, jmxPoolSize=10, cycleTime=300, v=10, hubPass=zenoss}
[2009-01-30 16:30:41,416] [INFO ] [main] 
com.zenoss.zenpacks.zenjmx.ZenJmxMain:68 - setting root logger to DEBUG
2009-01-30 16:30:41.450::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
2009-01-30 16:30:41.547::INFO:  jetty-6.0.2
2009-01-30 16:30:41.582::INFO:  Started SocketConnector @ 0.0.0.0:9988
DEBUG:zen.ZenJmxJavaClient:doCallback(): callback on deferred zenjmxjava proc 
is up
INFO:zen.ZenJMX:startZenjmx(): zenjmx java started
DEBUG:zen.ZenJMX:configTask(): fetching config
DEBUG:zen.ZenJMX:fetchConfig(): Fetching config from zenhub
DEBUG:zen.ZenJMX:Sending event {'severity': 0, 'component': 'zenjmx', 'agent': 
'zenjmx', 'summary': 'zenjmxjava started', 'manager': 'localhost', 'device': 
'localhost', 'eventClass': '/Status/JMX'}
DEBUG:zen.ZenJMX:Updated configCycleInterval config to 360
DEBUG:zen.ZenJMX:Loading classes ['Products.ZenModel.MinMaxThreshold']
DEBUG:zen.thresholds:Updating threshold ('zeneventlog cycle time', 
('localhost', ''))
DEBUG:zen.thresholds:Updating threshold ('zenmodeler cycle time', ('localhost', 
''))
DEBUG:zen.thresholds:Updating threshold ('zenperfsnmp cycle time', 
('localhost', ''))
DEBUG:zen.thresholds:Updating threshold ('zenping cycle time', ('localhost', 
''))
DEBUG:zen.thresholds:Updating threshold ('zenprocess cycle time', ('localhost', 
''))
DEBUG:zen.thresholds:Updating threshold ('zenwin cycle time', ('localhost', ''))
ERROR:zen.ZenJMX:[Failure instance: Traceback (failure with no frames): 
exceptions.AttributeError: CopiedFailure instance has no attribute '__len__'
]
Traceback (most recent call last):
  File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 49, in _next
    self.iter.next().addBoth(self._finish)
  File 
"/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenJMX-3.0-py2.4.egg/ZenPacks/zenoss/ZenJMX/zenjmx.py",
 line 80, in configTask
    driver.next()
  File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in 
result
    raise ex
AttributeError: CopiedFailure instance has no attribute '__len__'
INFO:zen.ZenJmxJavaClient:stop():stopping zenjmxjava
INFO:zen.ZenJMX:Daemon ZenJMX shutting down
DEBUG:zen.ZenJMX:removing service EventService
DEBUG:zen.ZenJMX:removing service 
ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService
INFO:zen.ZenJMX:zenjmx shutting down




Any ideas how to fix this?




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=30737#30737

-------------------- m2f --------------------



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

Reply via email to