After upgrading to .1898 I am getting periodic WMI overload's on my disk space sensors. It is happening to random servers.
Anything I can do prevent this? Before upgrading I did not have this issue at all.
Article Comments
I already have all the scan intervals set to 30 minutes. It was never an issue before the upgrade.
Jan, 2011 - Permalink
Does pausing sensors bring improvements for the unpaused sensors? Do you use the clustering feature in PRTG?
Jan, 2011 - Permalink
I have paused the troubled sensors and then resumed them and they will still be in an error state. Over this past weekend I had various disk space sensors go into an error state for 1-2 hours saying WMI overload.
Yes I am and have been using clustering with PRTG installed on 2 different servers in 2 different locations.
Jan, 2011 - Permalink
Please bear in mind, that all Windows Systems monitored by a PRTG Cluster (with 2 nodes) will have the doubled load in terms of WMI requests, compared to being only monitored by one PRTG installation.
Before 8.2, some WMI Sensors basically have had the same problem (most likely), and they went into a black/grey state, or maybe went into a yellow warning state for the period of one scanning interval. Now with 8.2 there is an explicit error for this condition (which was a WMI Overload before as well, if just hadn't had a name).
Jan, 2011 - Permalink
I removed the cluster and I am still getting these overload alerts on my disk space sensors.
Jan, 2011 - Permalink
I have since gone ahead and removed the cluster so the installation is now standalone. I have also changed most of the disk space sensors to a 1 hour scanning interval. I am still getting sporadic WMI overload errors from various sensors. I also upgraded to the most recent version (.1930)
Please advise on if there is something else I can do? Is it possible to avoid an email alert being sent out for these types of errors?
The issue is we keep getting false positive alerts and I don't want a real alert to be ignored.
Thanks,
Jan, 2011 - Permalink
I am also experiencing this issue since the upgrade to 1930 - sporadic WMI overload errors on many sensors; everything was working fine before the upgrade. Please advise!
Feb, 2011 - Permalink
We've had an issue which could lead to these PE054 errors. This is already addressed and will be fixed in the upcoming version.
Kind regards,
- Volker
Feb, 2011 - Permalink
Dear Jon,
please try using longer scanning intervals, and maybe also distribute the sensors over multiple remote probes.
Best Regards.
Jan, 2011 - Permalink