We only have a about 90 sensors of which most are ping or dicom echo. In the last few days the probe health has started to occasionally warn of health status with interval WMI delay varying between 60 and 148%. Normally the value sits at 0%. There are only a few (approx 12) wmi sensors and the server isn't under any real load. We are running 18.4.25261 Any help would be appreciated. Thanks Gareth

Article Comments

Hello Thomas,

Please follow these steps that will generate additional logs:

  1. Within PRTG please head to "Setup | System Administration | Administrative Tools | Probe Administrative Tools" and hit the button below "Write Probe Status Files".
  2. Please repeat step 1) 3 times with a 60 seconds delay before executing "Write Probe Status Files" again
  3. Open "PRTG Administration Tool" on the affected probe system that runs the sensors (PRTG Server or Remote Probe) and use the button "Send Logs to Paessler..." on tab "Logs and Infos".
    See also:

Kind regards,

Erhard


May, 2018 - Permalink

Dear Erhard, I have gathered the data, but our firewall rules prevent sending ftp data. It it possible to zip and email the data? Thanks Gareth


May, 2018 - Permalink

Hello Gareth,

Sure, use button "Open Log Folder" in admin tool and zip "Logs (System)" and send it by mail to support@paessler.com.

In case email delivery should not work, you can of course provide it at some other online space and send me the details or you can upload it manually to our ftp: Server Name: ftps.support.paessler.com (standard port 21, only supports TLS v.1 connections) FTP Mode: passive Username: customer Password: sl7aQyyJQrL50QH

Please contact us once the upload is complete. Please note that files on this server are not visible, you will not be able to get a directory listing.

Kind regards,

Erhard


May, 2018 - Permalink

Hello Erhard, I have emailed the logs. Thanks Gareth


May, 2018 - Permalink

Thank you, Gareth. I've received them and will get back to you after reviewing them.


May, 2018 - Permalink

The fault has been found with the underlying server. A number of Virtual machines on the physical server were loosing approximately 6 minutes every 75 minutes, then catching up. Once the VM was moved to a new server, the problem has resolved.


May, 2018 - Permalink

Hi Gareth,

Great, good to hear it's working now.

Kind regards,

Erhard


May, 2018 - Permalink