After upgrading to the latest PRTG version this moring, the local and cluster probe health has been in a warning (and sometimes down) state. With the following error;
"104 % Delay (Probe Interval Delay WMI) is above the error limit of 100 % Delay. WMI Sensors of this probe can not be scanned in their specified intervals. Try longer intervals or distribute load over probes."
We have increased the scan interval from 5 minutes to 10, this had no effect.
It seems to tie in to the amount of "Probe open requests" and increase in the "Available memory", which doesnt seem to make much sense.
Regards
Richard
Article Comments
Hi,
We started to see these issues after upgrading to PRTG Network Monitor 12.2.2.2157
Regards
Rich
Jun, 2012 - Permalink
Hi,
please send your PRTG logs and Probe States to support@paessler.com and refer to this KB entry. The logs are to be found in <PRTG Data Directory>\Logs (System) and your Probe States can be written in the WebGUI under Setup -> System Status -> Write Probe States. The Probe States are also placed in the Logs Directory.
Best regards
Jun, 2012 - Permalink
The logs and Probe States should be written to;
C:\Paessler\PRTG Network Monitor\Logs (System)\
However the only item in that directory is a blank text file "PRTGValidate.txt" (Modified 28/05/2012)
Please advise.
Jun, 2012 - Permalink
Hi,
please open the program "PRTG Server Administrator" and there switch to the tab "Logs". You can either send the logs directly from there or open the logfile directory also.
Best regards
Jun, 2012 - Permalink
Hi, Has this been fixed? we are seeing similar after upgrading to 14.4.13.3468.
Jan, 2015 - Permalink
Hi,
There is no known issue with the latest version of PRTG (14.4.13.3800+). Please forward your log files for analysis. Start the tool PRTG Administrator and click on the Send Logs to Paessler button or forward a support bundle by clicking on the Contact Support button in the bottom right corner of your Web GUI or Enterprise Console.
Best regards
Jan, 2015 - Permalink
Hi,
what precise version are you using? If not done yet, please perform a upgrade to the most recent version 12.2.2.2157 which should fix the issue.
Best regards
Jun, 2012 - Permalink