![]() |
![]() |
Subject: | zopectl log page error ValueError: 'event' is not a valid daemon name |
Author: | [Not Specified] |
Posted: | 2014-09-01 21:55 |
When I click into View Log page of daemon zopectl, error return as below. Please help. Version: Zenoss Core 4.2.4 SP71 .Thanks
A Zenoss error has occurred
ype:
Value: 'event' is not a valid daemon name
Traceback (most recent call last):
File "/opt/zenoss/lib/python/ZPublisher/Publish.py", line 126, in publish
request, bind=1)
.....
.....
File "/opt/zenoss/lib/python/zope/tales/tales.py", line 696, in evaluate
return expression(self)
File "/opt/zenoss/lib/python/zope/tales/pythonexpr.py", line 59, in __call__
return eval(self._code, vars)
File "
File "/opt/zenoss/Products/ZenModel/ZenossInfo.py", line 553, in getLogData
filename = self._getLogPath(daemon)
File "/opt/zenoss/Products/ZenModel/ZenossInfo.py", line 527, in _getLogPath
raise ValueError("%r is not a valid daemon name" % daemon)
ValueError: 'event' is not a valid daemon name
Subject: | Hi Anyone can help? |
Author: | [Not Specified] |
Posted: | 2014-09-08 21:05 |
Hi Anyone can help
Subject: | seeing same issue |
Author: | [Not Specified] |
Posted: | 2015-02-11 14:26 |
Did you find a solution to this issue with the event log error I am seeing the same thing and have found very little info related to it through various searches.
Zenoss version 4.2.5
Thanks
JB
Subject: | Got the same issue |
Author: | Tommy |
Posted: | 2015-05-28 03:11 |
Hi,
I find out the same problem with zopectl. Anyone know the solution
Tommy
-----
Zenoss Core 4.2.3
Linux: Red Hat Enterprise Linux Server release 5.2 (Tikanga) x86_64
Subject: | are you simply seeing this |
Author: | Andrew Kirch |
Posted: | 2015-05-28 10:29 |
are you simply seeing this error message, or is something breaking If something is breaking, please provide some detail as to what. Please also include if you are using remote collectors.
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
Subject: | When I try to enter into |
Author: | Tommy |
Posted: | 2015-05-28 11:21 |
When I try to enter into zopectl log I see error message as below:
Type:
Value: 'event' is not a valid daemon name
Traceback (most recent call last): File "/opt/zenoss/lib/python/ZPublisher/Publish.py", line 126, in publish request, bind=1) File "/opt/zenoss/lib/python/ZPublisher/mapply.py", line 77, in mapply if debug is not None: return debug(object,args,context) File "/opt/zenoss/lib/python/ZPublisher/Publish.py", line 46, in call_object result=apply(object,args) # Type s
Additionally I found error message in zenperfsnmp.log:
2015-05-28 16:03:29,296 WARNING zen.zenperfsnmp: No service named 'EventService': ZenHub may be disconnected
2015-05-28 16:03:29,297 ERROR zen.maintenance: Maintenance failed. Message from hub: ZenHub is down
After this zenperfsnmp didn't work though daemon was up.
I tried some things (restart zenoss, restart mysql) and at least I removed *.pickle files (when Zenoss was down).
Now zenperfsnmp work correctly (mean connected to zenhub) but I see new messages, like this:
2015-05-28 18:10:06,143 ERROR zen.netsnmp: Exception in _callback 592973779
Traceback (most recent call last):
File "/opt/zenoss/lib/python/pynetsnmp/netsnmp.py", line 376, in _callback
sess.timeout(reqid)
File "/opt/zenoss/lib/python/pynetsnmp/twistedsnmp.py", line 236, in timeout_
d = self.defers.pop(reqid)[0]
KeyError: 592973779
I also receive a lot of:
2015-05-28 18:10:08,678 ERROR zen.zenperfsnmp: SNMP get did not return result: ups-lub-armiikrajowej 1.3.6.1.4.1.318.1.1.1.2.2.1.0
2015-05-28 18:10:08,678 WARNING zen.zenperfsnmp: Error reading value for ['batteryCapacity'] (1.3.6.1.4.1.318.1.1.1.2.2.1.0) on ups-lub-armiikrajowej
2015-05-28 18:10:08,679 ERROR zen.zenperfsnmp: SNMP get returned unexpected OID: ups-lub-armiikrajowej 1.3.6.1.6.3.15.1.1.2.0
2015-05-28 18:10:09,474 ERROR zen.zenperfsnmp: SNMP get did not return result: ups-lub-armiikrajowej 1.3.6.1.4.1.318.1.1.1.4.2.2.0
2015-05-28 18:10:09,474 WARNING zen.zenperfsnmp: Error reading value for ['Output Frequency in Herz'] (1.3.6.1.4.1.318.1.1.1.4.2.2.0) on ups-lub-armiikrajowej
2015-05-28 18:10:09,474 ERROR zen.zenperfsnmp: SNMP get returned unexpected OID: ups-lub-armiikrajowej 1.3.6.1.6.3.15.1.1.2.0
2015-05-28 18:10:10,271 ERROR zen.zenperfsnmp: SNMP get did not return result: ups-lub-armiikrajowej 1.3.6.1.4.1.318.1.1.1.4.2.4.0
2015-05-28 18:10:10,271 WARNING zen.zenperfsnmp: Error reading value for ['Load Current', 'Output Current'] (1.3.6.1.4.1.318.1.1.1.4.2.4.0) on ups-lub-armiikrajowej
2015-05-28 18:10:10,271 ERROR zen.zenperfsnmp: SNMP get returned unexpected OID: ups-lub-armiikrajowej 1.3.6.1.6.3.15.1.1.2.0
2015-05-28 18:10:11,068 ERROR zen.zenperfsnmp: SNMP get did not return result: ups-lub-armiikrajowej 1.3.6.1.4.1.318.1.1.1.4.2.3.0
2015-05-28 18:10:11,068 WARNING zen.zenperfsnmp: Error reading value for ['batteryOutputLoad'] (1.3.6.1.4.1.318.1.1.1.4.2.3.0) on ups-lub-armiikrajowej
2015-05-28 18:10:11,068 ERROR zen.zenperfsnmp: SNMP get returned unexpected OID: ups-lub-armiikrajowej 1.3.6.1.6.3.15.1.1.2.0
2015-05-28 18:10:14,100 ERROR zen.zenperfsnmp: SNMP get returned empty value: 10.18.62.41 1.3.6.1.4.1.9600.1.1.2.10.0
2015-05-28 18:10:14,100 WARNING zen.zenperfsnmp: Error reading value for ['memoryPagesPerSec'] (1.3.6.1.4.1.9600.1.1.2.10.0) on 10.18.62.41
2015-05-28 18:10:14,124 ERROR zen.zenperfsnmp: SNMP get returned empty value: 10.18.62.41 1.3.6.1.4.1.9600.1.1.1.1.15.2.68.58
2015-05-28 18:10:14,124 WARNING zen.zenperfsnmp: Error reading value for ['D:'] (1.3.6.1.4.1.9600.1.1.1.1.15.2.68.58) on 10.18.62.41
2015-05-28 18:10:14,147 ERROR zen.zenperfsnmp: SNMP get returned empty value: 10.18.62.41 1.3.6.1.4.1.9600.1.1.2.2.0
At last I run script "zenfixit.py", but got an error:
Cleaning up invalid entries from catalogs:
Traceback (most recent call last):
File "/home/zenoss/bin/zenfixit.py", line 435, in
zfi.run()
File "/home/zenoss/bin/zenfixit.py", line 29, in run
self.fixCatalogs()
File "/home/zenoss/bin/zenfixit.py", line 196, in fixCatalogs
dmd.Devices.componentSearch,
AttributeError: componentSearch
Have you any idea what happen in my instance :)
Thanks in advance.
Tommy
PS: Sorry for my bad english
Subject: | I'd suggest getting up to 4.2 |
Author: | Andrew Kirch |
Posted: | 2015-05-29 11:53 |
I'd suggest getting up to 4.2.5. The OID errors look like a zenpack issue (monitoring a UPS), and are not related to the "event" is not a valid daemon name. Once you're on 4.2.5 instead of using Zenfixit, install the latest ZUP (available on the wiki.zenoss.org zenup page), and run the zenoss toolkit (available on github)
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
< |
Previous Device Issues Portlet No records found |
Next Zencommand not collecting after reboot remote host |
> |