I have a recurring series of failures in the zeneventlog.log such as the following, and we seem to be failing to detect Windows event log events after Zenoss tells us it's "removing" a particular machine:
Code: 2007-11-09 03:28:40 WARNING zen.zeneventlog: ehhctx02.domain.local wmi connection failed: Desc [scode=1726] 2007-11-09 03:28:40 WARNING zen.zeneventlog: removing ehhctx02.domain.local 2007-11-09 03:28:40 WARNING zen.zeneventlog: PBTS0301.domain.local wmi connection failed: Desc [scode=1726] 2007-11-09 03:28:40 WARNING zen.zeneventlog: removing PBTS0301.domain.local 2007-11-09 03:28:40 WARNING zen.zeneventlog: ddwh0302.domain.local wmi connection failed: Desc [scode=1726] 2007-11-09 03:28:40 WARNING zen.zeneventlog: removing ddwh0302.domain.local Note: I changed the zeneventlog.py code to get it to log the error code of these failures that before simply said "wmi connection failed: Desc." The error code is 1726, which from googling apparently is RPC_S_CALL_FAILED. Does anyone have a workaround for this or any information as to its cause? I've read another post (http://community.zenoss.com/forums/viewtopic.php?t=3009) indicating that the error is caused by machines being on other subnets but in looking at our stream of errors that's not the case. The errors occur regardless of whether the monitored machine is on the same subnet as the Zenoss server or not. Note that for these machines, I can go to the Zenoss server shell and issue wmic calls to these boxes that succeed, so the WMI connectivity seems to be working. Help!! -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=13000#13000 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
