WMI datacollection stops after changes in Schedules Outages

Alejandro,

i will test version 1.8.15 in the next days and give you feedback.

I tried many combinations and I couldn't reproduce the problem. It is working for me with latest compilations of 1.8.15-SNAPSHOT and 1.9.92-SNAPSHOT. The target WMI machine has Windows 2008 Enterprise (32 bits).

This is what I tried (in all cases, WMI data collection worked as expected):

• Delete an existing scheduled outage

• Create a scheduled outages which affects a node that does not support WMI

• Create a scheduled outages which affects a node that has WMI enabled (WMI stop collect only for the period defined in the scheduled outage)

• Create a scheduled outages which affects all nodes

I'll close this as I cannot reproduce the problem. If you are able to reproduce it (with a recent version of OpenNMS), please I'll really appreciate if you provide me the detailed steps about how to reproduce the problem and include the relevant configuration files and logs that will help me to track down the problem.

Remember that the WebUI for Scheduled Outages is a little tricky, so you should take extra care when creating the scheduled outages and verify the content after you finish the creation/edition of any scheduled outage.

Stefan,

It will be wonderful if you provide a step by step procedure about how to reproduce the problem based on your current configuration, and also provide the content of collectd-configuration.xml and poll-outages.xml