Hi, in my company we are observing problems whith Custom EXE sensor. Either it is a Powershell or EXE custom made program, it is at some random point not recieving data. From server side we can see that this process is hanging in "unknown" state. After random period of time sensor is again alive but hanged process is left not closed in process list.
Our custom execs are working correctly when run manually, they are not using any GUI interfaces, this are mainly connected with web browsing atomation and speed tests using phanotmjs or iexplore. This was tested on few instances of PRTG, also on brand new instance with almost non other sensors. Sensor have well configured xml resonse.
We have tried to set shour timouts for this sensors but it looks like this timout do nothing - no matter what we set it is not helping.
Any ideas what can be done to have this working correctly?
Article Comments
.4999 version? not the .4666?
We will try to update it to the newest version next week, then I will be able to check this.
Jul, 2016 - Permalink
Hi, we have upgraded PRTG version but problem is still occuring. Custom EXE sensors are stopping and not working in random way. Processes started by them are just hung and unitill they die/ are killed sensor dont start another checkout.
When processes are not freezed everything is wokring correctly, response is translated to PRTG values. Also minotored pages are working constantly.
Solution for this would be correctly working timeout set in sensor but it is not trying to stop proces after set time period.
Jul, 2016 - Permalink
Is it possible that the application you're starting with the sensor is somewhat hanging and the parent process (which is the PRTG sensor) is being shot down by PRTG (or Windows), leaving the original process hanging in the air?
Jul, 2016 - Permalink
It is quite possible, we are running process which is starting phantomjs (it is a small automation scenario for checking web page speed and functionality based on Selenium), it is running for some time, then phantomjs process is freezing.
Is it possible that PRTG timeout option will kill also a child processes?
Jul, 2016 - Permalink
If the piggyback process you're starting with the sensor doesn't deliver data, then it will be killed by Windows. Leaving phantomJS orphaned with no process to report back to...Any way for you to re-arrange the way you do this?
Jul, 2016 - Permalink
Are you running the latest PRTG version? We had some problems with our EXE execution process which are fixed in the .4666 version.
Jul, 2016 - Permalink