What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Custom EXE - This sensor has not received data

Votes:

0

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?

custom custom-script-exe prtg

Created on Jul 8, 2016 2:21:38 PM



9 Replies

Votes:

0

Are you running the latest PRTG version? We had some problems with our EXE execution process which are fixed in the .4666 version.

Created on Jul 11, 2016 10:27:02 AM by Stephan Linke [Paessler Support]

Last change on Jul 13, 2016 6:31:10 AM by Stephan Linke [Paessler Support]



Votes:

0

.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.

Created on Jul 12, 2016 2:05:19 PM



Votes:

0

Indeed .4666 - fixed it in my post :)

Created on Jul 13, 2016 6:31:25 AM by Stephan Linke [Paessler Support]



Votes:

0

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.

Created on Jul 25, 2016 11:26:28 AM



Votes:

0

What version are you currently running?

Created on Jul 25, 2016 12:52:22 PM by Stephan Linke [Paessler Support]



Votes:

0

Currently Installed Version: 16.3.24.4980+

Created on Jul 25, 2016 12:57:07 PM



Votes:

0

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?

Created on Jul 25, 2016 1:44:36 PM by Stephan Linke [Paessler Support]



Votes:

0

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?

Created on Jul 27, 2016 3:32:28 PM



Votes:

0

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?

Created on Jul 28, 2016 7:41:26 AM by Stephan Linke [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.