Client timeout caused by WMI tries to read performance counter

CMK version: 2.2.0p32

Hello!
On some of our Terminalservers we experience some client timeouts after half a day of operations. In the check_mk.log on the client i see where the timeout is coming from.


The WMI Timout is already set to 10s, but i guess that counts for every single WMI call that the client is doing and not for all WMI calls together. Overall Clienttimeout is set to 60s. The problem is fixable with a reboot from the PVS image.

WMI in general looks operational on that server. Is there a way i can blacklist some performance counters from beeing called over WMI?

Cheers

We have such issues from time to time. In rare cases we couldn’t fix. In general WMI is good but the implementation is disappointing. Even that Microsoft knows about the issues since decades they do nothing.
As far as I know you can only disable sections in the agent. You may can limit with access rights on WMI side but checkmk will complain if not all metrics sent for a specific section.

Have a look here:

https://checkmk.atlassian.net/wiki/spaces/KB/pages/9472924/Troubleshoot+Windows+System+and+Performance+Counters

Please let me know if you had been able to fix it and how.

regards

Michael

Hello,
we disabled these sections for all windows agnts by default:

This helped us to solved most of the WMI errors.

Regards
Claus

1 Like

perfect, if it was done because of my recommendation I would be happy if you can mark my post as solution.

regards

Michael

Sry no , it was 2 years experience with more than 3000 Windows server. :wink:

Ahh, sorry I mistake you with the TO

For my specific problem here, disable the MS Exchange counts fix the problem.