Custom Sensors - PE008

Hi,
What version of PRTG are you using? Also, may I ask what the script does exactly (if possible please post the same here)?
Best regards

Hi,

The Script is for a reverse ping sensor. We need it to show an alert when it responds and OK when its down.

Script is a .bat file and its the following:

@echo off

ping -n 2 %1|Findstr /I /C:"timed out" /C:"host unreachable" > nul
if %errorlevel%==0 (echo 0:OK - Ping to %1 failed && EXIT /B 0) else (echo 1:Error - Ping to %1 successful - PCI Security Threat && EXIT /B 2)

The script works fine but PRTG just keeps dropping and says it cannot fine the file.

PRTG version: 14.3.10.2422

Adam

Hi,
The script looks ok to me. How much sensors using this script have you running?
Have you tried defining a Mutex on tab Settings of the sensor?

hi,

I have just tried adding a mutex name but it keeps doing the same thing. It appears to work for 4 minutes then stop working.

I have uploaded a Image here so you can see: http://postimg.org/image/7c0v9syeb/

Adam

Hi,
do you have any AV solution running on the machine the script is executed? If so, please try adding a exception for this particular script. Does that have any effect on the sensor?
Additionally, please try changing the scanning interval of the sensor to, e.g. 5 or 10 minutes and let it run for some time. What results do you get then?

Hi, I have just started to look at this again and we are having the same problem. Mutex is set, AV disabled on server running the remote probe and every 4-7 minutes it stops working giving an PE008 error for 4-7 minutes then comes back again.

During the period it shows the error if you try and create a new Custom EXE/SCript sensor and select the custom .bat or .ps1 file it actually missing from the list. I dont think its an issue with the script itself it just appears that PRTG no longer recognizes or is able to access the file.

Hi,
Thank you for getting back to me. I will forward your case to our testing team and we will try to recreate your issue in our lab as we don't have seen this precise behaviour. At the moment I assume that this might be related to the structure of the scrip you are executing (resp. the used command). However, I will get back to you as soon as I know more.

Has any progress been made on this? I'm having nearly the same issue. Custom EXE sensor (a small utility I wrote in C#) applied to approximately 40 servers. Works fine on around 35 of them, but returns the "file not found" error on the rest. I've tried with and without a Mutex, and with a scanning interval of one hour, with no change.

Thanks, James

Hi, we are still testing this but so far were unable to recreate the issue. However, it might be that our admins found something here. Let me verify and I will get back to you.

Hi all,
could you forward your system logs to support@paessler.com?
When doing so, please refer to this thread. Thanks!

I just uploaded the log files per your request. There was no way to refer to this thread using the "Send Logs to Paessler" function from within PRTG Administrator. I did separately e-mail support and reference this thread. Thanks.

Thanks, the logs were received. I will forward them to our devs to have a look at the same.

Has anyone found a solution for this problem?

Hi there,

Unfortunately, there was no solution found. Please note that this thread is from 2014.

What version of PRTG do you use? What are you sensor settings? What kind of Custom Script are you executing?

Best regards.

We are using version 19 of the PRTG agent and are using a custom script to check the status of our Veeam Backups using PSx64.exe with a Powershell Script called 'PRTG-VeeamBRStats.ps1'. This check happens every 5 mins and alternates from and OK status to a PE008. We have this same setup running on various other servers in our environment with no issue.

Hi there,

That might be a guess in the blue, but do you run an AntiVirus System on the Probe Server that might prevent PRTG form executing the script?

Best regards.

Hey Dariusz,

There is no antivirus installed on this machine.

Could you check the process being executed using ProcMon, if it's accessing a folder that may not exist or a locked file, something like that? That's just an educated guess, though.

PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team