Right. That's the intended result of the most recent sprint (now that we're past the bugs). Granted, the error message needs to be improved. Basically, the call to the windows machine is timing out.
If you are comfortable editing the .py files, go ahead and increase the timeout. Change the value of MAX_WAIT_FOR_WMI_REQUEST in the ZenWin/*.py files (this will be configurable in the future). I doubt this will help, but I'm very interested in getting feedback for the right default value. If you are seeing failures to only some devices, test the connectivity with this command: Code: $ wmic -U Domain/User%Passwd //device "select name from Win32_Service where State='Running'" Substitute your Domain, User and Passwd for the device in question. We're still looking for patterns to the failure, so if you have problems, please post details about your environment (networking gear, network topology, firewalls, etc). Thank you all for sticking with it. This will help us have a much more robust 2.2 release. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=17163#17163 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
