![]() |
![]() |
Subject: | Errors on the localhost. |
Author: | [Not Specified] |
Posted: | 2015-08-03 05:00 |
Hi,
Currently I am getting the following errors in Zenoss for the localhost:
ZenPacks.zenoss.WindowsMonitor.services.WinServiceConfig.WinServiceConfig
Unhandled exception in zenhub service ZenPacks.zenoss.WindowsMonitor.services.WinServiceConfig.WinServiceConfig: 0x087bea
ZenPacks.zenoss.PythonCollector.services.PythonConfig.PythonConfig
Unhandled exception in zenhub service ZenPacks.zenoss.PythonCollector.services.PythonConfig.PythonConfig: 0x087bea
Products.ZenHub.services.ProcessConfig.ProcessConfig
Unhandled exception in zenhub service Products.ZenHub.services.ProcessConfig.ProcessConfig: 0x087bea
ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService.ZenJMXConfigService
Unhandled exception in zenhub service ZenPacks.zenoss.ZenJMX.services.ZenJMXConfigService.ZenJMXConfigService: 0x087bea
Products.ZenHub.services.CommandPerformanceConfig.CommandPerformanceConfig
Unhandled exception in zenhub service Products.ZenHub.services.CommandPerformanceConfig.CommandPerformanceConfig: 0x087bea
Products.ZenHub.services.SnmpPerformanceConfig.SnmpPerformanceConfig
Unhandled exception in zenhub service Products.ZenHub.services.SnmpPerformanceConfig.SnmpPerformanceConfig: 0x087bea
Products.ZenHub.services.PingPerformanceConfig.PingPerformanceConfig
Unhandled exception in zenhub service Products.ZenHub.services.PingPerformanceConfig.PingPerformanceConfig: 0x102573
ZenPacks.zenoss.WindowsMonitor.services.WinPerfConfig.WinPerfConfig
Unhandled exception in zenhub service ZenPacks.zenoss.WindowsMonitor.services.WinPerfConfig.WinPerfConfig: 0x087bea
I can close the errors, and they come back within a few hours. Otherwise Zenoss seems to be running OK. Clinging on to Google, I came up with this article:
http://community.zenoss.org/message/74254#74254
However, this does not enlighten me how I should go about fixing the issue myself. Any help appreciated.
Ben
Subject: | Your link points to a |
Author: | Andrew Kirch |
Posted: | 2015-08-03 09:26 |
Your link points to a database issue. Without more information I can't say whether it's right or wrong, but assuming it's right, I'd suggest starting by running the Zenoss Toolkit. You may not have poskey errors (or you may have them in other logs, and can't see them) but I'd start here: http://wiki.zenoss.org/Troubleshooting_Zenoss_PosKey_Errors
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: | Hi, |
Author: | [Not Specified] |
Posted: | 2015-08-04 02:03 |
Hi,
Thanks for the reply. Firstly I took a snapshot, then I ran the scripts in the toolkit, and it did, indeed, seem to find some errors. It seems I had a dangling object. I've known that since I was a boy, however confirmation of this fact seems to have cured the errors that were coming up on Zenoss.
I will continue to monitor today, and if all seems to be well, I'll let you know.
Subject: | Seems to be working without |
Author: | [Not Specified] |
Posted: | 2015-08-04 07:33 |
Seems to be working without issue today. So case closed as far as I know. Many thanks for your help.
Subject: | glad we could help! Also |
Author: | Andrew Kirch |
Posted: | 2015-08-04 13:30 |
glad we could help! Also hilarious response, I lol'd :)
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 zenpacklib: !ZenPackSpec |
Next problem with installing zenpacks |
> |