Hi
My Zenoss box (v2.2.4) is logging some tracebacks...
These from Zenwin:
2008-12-04 19:59:47 INFO zen.zenwin: Daemon zenwin shutting down
2008-12-04 19:59:47 ERROR zen.zenwin: Error processing main loop
Traceback (most recent call last):
File "/home/zenoss/Products/ZenWin/WinCollector.py", line 103, in scanCycle
self.wmiprobs = [e[0] for e in driver.next()]
File "/home/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-12-04 19:59:47 INFO zen.zenwin: zenwin shutting down
2008-12-04 19:59:47 ERROR watchdog: Timeout: getting status from process
2008-12-04 20:09:47 ERROR watchdog: Restarting zenwin
2008-12-04 20:09:50 WARNING zen.zenwin: Reconnected to ZenHub
2008-12-04 20:09:50 INFO zen.zenwin: Setting configCycleInterval to 360
2008-12-04 20:09:50 INFO zen.zenwin: Starting zenwin
2008-12-04 20:22:50 INFO zen.zenwin: delete pidfile
/home/zenoss/var/zenwin-localhost.pid
2008-12-04 20:22:50 INFO zen.zenwin: Daemon zenwin shutting down
2008-12-04 20:22:50 ERROR zen.zenwin: Error processing main loop
Traceback (most recent call last):
File "/home/zenoss/Products/ZenWin/WinCollector.py", line 103, in scanCycle
self.wmiprobs = [e[0] for e in driver.next()]
File "/home/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-12-04 20:22:50 INFO zen.zenwin: zenwin shutting down
2008-12-04 20:22:51 ERROR watchdog: Timeout: getting status from process
2008-12-04 20:32:51 ERROR watchdog: Restarting zenwin
2008-12-04 20:32:53 WARNING zen.zenwin: Reconnected to ZenHub
2008-12-04 20:32:53 INFO zen.zenwin: Setting configCycleInterval to 360
2008-12-04 20:32:53 INFO zen.zenwin: Starting zenwin
And from Zeneventlog:
2008-12-04 19:59:57 INFO zen.zeneventlog: delete pidfile
/home/zenoss/var/zeneventlog-localhost.pid
2008-12-04 19:59:57 INFO zen.zeneventlog: Daemon zeneventlog shutting down
2008-12-04 19:59:57 ERROR zen.zeneventlog: Error processing main loop
Traceback (most recent call last):
File "/home/zenoss/Products/ZenWin/WinCollector.py", line 103, in scanCycle
self.wmiprobs = [e[0] for e in driver.next()]
File "/home/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-12-04 19:59:57 INFO zen.zeneventlog: zeneventlog shutting down
2008-12-04 19:59:57 ERROR watchdog: Timeout: getting status from process
2008-12-04 20:09:57 ERROR watchdog: Restarting zeneventlog
2008-12-04 20:09:59 WARNING zen.zeneventlog: Reconnected to ZenHub
2008-12-04 20:09:59 INFO zen.zeneventlog: Setting configCycleInterval to 360
2008-12-04 20:09:59 INFO zen.zeneventlog: Setting eventlogCycleInterval to 60
2008-12-04 20:09:59 INFO zen.zeneventlog: Starting zeneventlog
2008-12-04 20:09:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:09:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:10:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:10:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:11:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:11:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:12:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:12:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:13:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:13:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:14:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:14:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:15:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:15:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:16:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:16:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:17:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:17:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:18:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:18:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:19:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:19:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:20:59 INFO zen.zeneventlog: Com InterfaceCount: 1
2008-12-04 20:20:59 INFO zen.zeneventlog: Com GatewayCount: 1
2008-12-04 20:23:00 INFO zen.zeneventlog: delete pidfile
/home/zenoss/var/zeneventlog-localhost.pid
2008-12-04 20:23:00 INFO zen.zeneventlog: Daemon zeneventlog shutting down
2008-12-04 20:23:00 ERROR zen.zeneventlog: Error processing main loop
Traceback (most recent call last):
File "/home/zenoss/Products/ZenWin/WinCollector.py", line 103, in scanCycle
self.wmiprobs = [e[0] for e in driver.next()]
File "/home/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-12-04 20:23:00 INFO zen.zeneventlog: zeneventlog shutting down
2008-12-04 20:23:00 ERROR watchdog: Timeout: getting status from process
2008-12-04 20:33:00 ERROR watchdog: Restarting zeneventlog
2008-12-04 20:33:02 WARNING zen.zeneventlog: Reconnected to ZenHub
2008-12-04 20:33:02 INFO zen.zeneventlog: Setting configCycleInterval to 360
2008-12-04 20:33:02 INFO zen.zeneventlog: Setting eventlogCycleInterval to 60
2008-12-04 20:33:03 INFO zen.zeneventlog: Starting zeneventlog
I did originally have some Windows servers monitored, but they are Win2k8 and
have problems with the version of Zenoss we run in production. I've tried a
newer beta that resolves those problems, but for now we simply don't monitor
those boxes - they've been deleted from the system.
Which makes it seem odd that Zenwin would fail?
Anyone any ideas how I can troubleshoot this?
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=28734#28734
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users