Well, the problem has occurred on the new Zenoss server too. It began
happening after we moved the Windows devices under /Servers/Windows.
Looking through the logs, it seems that it stops after the zenwin process
reports some errors - these errors are visible in the zeneventlog:
Code:
2007-08-30 14:42:40 ERROR zen.zeneventlog: WMI connect error on Win2KServer1:
com_error(-2147024891): DOS code 0x80070005
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenWin/zeneventlog.py", line 52, in
updateDevices
self.devices[name] = self.getWatcher(name,user,passwd,sev)
File "/usr/local/zenoss/Products/ZenWin/zeneventlog.py", line 74, in
getWatcher
c.connect()
File "/usr/local/zenoss/Products/ZenWin/wmiclient.py", line 51, in connect
self.flags,self.valueset)
File "usr/local/zenoss/lib/python/win32com/client.py", line 33, in
ConnectServer
services = pywmi.WBEM_ConnectServer(name, namespace, user, passwd, locale,
flags, authority, valueset)
com_error: com_error(-2147024891): DOS code 0x80070005
2007-08-30 14:42:41 ERROR zen.zeneventlog: WMI connect error on Win2KServer2:
com_error(-2147024891): DOS code 0x80070005
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenWin/zeneventlog.py", line 52, in
updateDevices
self.devices[name] = self.getWatcher(name,user,passwd,sev)
File "/usr/local/zenoss/Products/ZenWin/zeneventlog.py", line 74, in
getWatcher
c.connect()
File "/usr/local/zenoss/Products/ZenWin/wmiclient.py", line 51, in connect
self.flags,self.valueset)
File "usr/local/zenoss/lib/python/win32com/client.py", line 33, in
ConnectServer
services = pywmi.WBEM_ConnectServer(name, namespace, user, passwd, locale,
flags, authority, valueset)
com_error: com_error(-2147024891): DOS code 0x80070005
2007-08-30 14:44:42 ERROR zen.zeneventlog: ERROR_CONNECTION_REFUSED: The remote
computer refused the network connection. (1225)
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenWin/zeneventlog.py", line 52, in
updateDevices
self.devices[name] = self.getWatcher(name,user,passwd,sev)
File "/usr/local/zenoss/Products/ZenWin/zeneventlog.py", line 74, in
getWatcher
c.connect()
File "/usr/local/zenoss/Products/ZenWin/wmiclient.py", line 51, in connect
self.flags,self.valueset)
File "usr/local/zenoss/lib/python/win32com/client.py", line 33, in
ConnectServer
services = pywmi.WBEM_ConnectServer(name, namespace, user, passwd, locale,
flags, authority, valueset)
com_error: com_error(1225): DOS code 0x000004c9
2007-08-30 14:44:44 ERROR zen.zeneventlog: ERROR_CONNECTION_REFUSED: The remote
computer refused the network connection. (1225)
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenWin/zeneventlog.py", line 52, in
updateDevices
self.devices[name] = self.getWatcher(name,user,passwd,sev)
File "/usr/local/zenoss/Products/ZenWin/zeneventlog.py", line 74, in
getWatcher
c.connect()
File "/usr/local/zenoss/Products/ZenWin/wmiclient.py", line 51, in connect
self.flags,self.valueset)
File "usr/local/zenoss/lib/python/win32com/client.py", line 33, in
ConnectServer
services = pywmi.WBEM_ConnectServer(name, namespace, user, passwd, locale,
flags, authority, valueset)
com_error: com_error(1225): DOS code 0x000004c9
2007-08-30 14:50:47 ERROR zen.zeneventlog: ERROR_LOGON_FAILURE: Logon failure:
unknown user name or bad password. (1326)
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenWin/zeneventlog.py", line 52, in
updateDevices
self.devices[name] = self.getWatcher(name,user,passwd,sev)
File "/usr/local/zenoss/Products/ZenWin/zeneventlog.py", line 74, in
getWatcher
c.connect()
File "/usr/local/zenoss/Products/ZenWin/wmiclient.py", line 51, in connect
self.flags,self.valueset)
File "usr/local/zenoss/lib/python/win32com/client.py", line 33, in
ConnectServer
services = pywmi.WBEM_ConnectServer(name, namespace, user, passwd, locale,
flags, authority, valueset)
com_error: com_error(1326): DOS code 0x0000052e
The servers it is reporting problems against are Windows 2000 Server machines.
I may try setting them to WMIIgnore in their zProperties pages.
I do think that the processes should be able to handle errors like these
without falling over.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=10331#10331
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
