I'm still test-running ZenOss and upgraded to 2.2.4 hoping that it would behave less oddly :-)
Now I have an event concerning a failing WinService which keeps coming back despite the fact I've set the WinService not to monitor both globally and inside the server object and I explicitly deleted the service from the server-object WinServices list. For testing purposes I previously set the WinService "MSSQLServerADHelper" to "Monitor: True" on the global object. I remodelled a few windows servers where he found this service. The service was not running on those servers so after some time Zenoss told me the service failed on that server. Indeed, that service is not running and is in fact disabled on all servers. So I set "Monitor: False" again on the global object. And the WinService also disappeared from the servers object OS-view. I moved the events to history. All clear I thought. BUT, the event reappeared after a few seconds for only ONE server. I tried everything by adding the WinService back to that specific server-object and then deleting it, or setting the monitor to false on the server-object only.. But the event keeps coming back despite the WinService not being listed in the WinServices list of the server object. How is this possible that this service is still being polled by ZenOss on this one server while I explicitly ask ZenOss not to monitor the service both locally and globally ? -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=25676#25676 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
