James,
Thanks for the response. Hopefully someone from Zenoss would like
to comment as well.
Here are some additional log entries from today. As I said, the zenwin
process seems unstable and error/clear events are generated regularly.
2008-09-08 11:43:57 ERROR watchdog: Timeout: getting status from process
2008-09-08 11:45:56 ERROR watchdog: Restarting zenwin
2008-09-08 11:45:58 WARNING zen.zenwin: Reconnected to ZenHub
2008-09-08 11:45:58 INFO zen.zenwin: Setting configCycleInterval to 360
2008-09-08 11:46:00 INFO zen.zenwin: Starting zenwin
2008-09-08 11:48:10 ERROR watchdog: Timeout: getting status from process
2008-09-08 11:53:57 ERROR watchdog: Restarting zenwin
2008-09-08 11:53:59 WARNING zen.zenwin: Reconnected to ZenHub
2008-09-08 11:53:59 INFO zen.zenwin: Setting configCycleInterval to 360
2008-09-08 11:54:00 INFO zen.zenwin: Starting zenwin
2008-09-08 11:56:07 WARNING zen.zenwin: WMI Connection to
rpnyex01.company.com went down
2008-09-08 11:56:07 ERROR watchdog: Received input on report socket:
probably EOF
2008-09-08 11:56:07 ERROR watchdog: Unable to report to the watchdog.
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenUtils/Watchdog.py", line 246, in niceDoggie
self.sock.send('%d\n' % cycleTime)
error: (32, 'Broken pipe')
2008-09-08 11:56:07 ERROR zen.zenwin: Error processing main loop
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenWin/WinCollector.py", line 119, in scanCycle
deferreds = self.processLoop()
File "/opt/zenoss/Products/ZenWin/zenwin.py", line 137, in processLoop
self.niceDoggie(self.winCycleInterval)
File "/opt/zenoss/Products/ZenUtils/ZenDaemon.py", line 215, in niceDoggie
self.reporter.niceDoggie(timeout)
File "/opt/zenoss/Products/ZenUtils/Watchdog.py", line 249, in niceDoggie
sys.exit(1)
SystemExit: 1
2008-09-08 11:56:07 INFO zen.zenwin: delete pidfile
/opt/zenoss/var/zenwin-localhost.pid
2008-09-08 11:56:07 INFO zen.zenwin: Daemon zenwin shutting down
2008-09-08 11:56:07 ERROR zen.zenwin: Error processing main loop
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenWin/WinCollector.py", line 117, in scanCycle
self.wmiprobs = [e[0] for e in driver.next()]
File "/opt/zenoss/Products/ZenUtils/Driver.py", line 58, in next
raise ex
PBConnectionLost: [Failure instance: Traceback (failure with no frames):
twisted.internet.error.ConnectionLost: Connection to the other side was
lost in a non-clean fashion: Connection lost.
]
2008-09-08 11:56:07 INFO zen.zenwin: zenwin shutting down
2008-09-08 11:56:07 ERROR watchdog: Timeout: getting status from process
2008-09-08 11:58:10 ERROR watchdog: Restarting zenwin
2008-09-08 11:58:12 WARNING zen.zenwin: Reconnected to ZenHub
2008-09-08 11:58:12 INFO zen.zenwin: Setting configCycleInterval to 360
2008-09-08 11:58:13 INFO zen.zenwin: Starting zenwin
2008-09-08 12:00:25 ERROR watchdog: Timeout: getting status from process
2008-09-08 12:06:07 ERROR watchdog: Restarting zenwin
2008-09-08 12:06:10 WARNING zen.zenwin: Reconnected to ZenHub
2008-09-08 12:06:10 INFO zen.zenwin: Setting configCycleInterval to 360
2008-09-08 12:06:11 INFO zen.zenwin: Starting zenwin
2008-09-08 12:08:22 ERROR watchdog: Timeout: getting status from process
2008-09-08 12:10:25 ERROR watchdog: Restarting zenwin
2008-09-08 12:10:27 WARNING zen.zenwin: Reconnected to ZenHub
2008-09-08 12:10:27 INFO zen.zenwin: Setting configCycleInterval to 360
2008-09-08 12:10:28 INFO zen.zenwin: Starting zenwin
Clayton Taylor Dillard
Network Security Enthusiast
Aim for the truth - it works!
James Pulver wrote:
> 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
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
