I think it just means you're getting close to your cycle time to
complete pollings of WMI. So Zenoss either a) has too many windows
devices to poll via WMI for the cycle time or b) something is causing
some of your Windows devices to hang up and not respond for a while on a
WMI query occasionally.
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
cdillardhsp wrote:
I'm getting off and on zenwin cycle time errors. The error clears after a
period of time, then reappears.
threshold of zenwin cycle time exceeded: current value 122.32
Zenwin log says:
2008-09-06 21:46:27 INFO zen.zenwin: Async config notification
2008-09-06 21:48:35 ERROR watchdog: Timeout: getting status from process
2008-09-06 21:58:35 ERROR watchdog: Restarting zenwin
2008-09-06 21:58:37 WARNING zen.zenwin: Reconnected to ZenHub
2008-09-06 21:58:37 INFO zen.zenwin: Setting configCycleInterval to 360
2008-09-06 21:58:38 INFO zen.zenwin: Starting zenwin
Anybody have any ideas?
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=24761#24761
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
