Hi *,
After upgrading to PRTG version 9.1.6.1962 (coming from some 9.1.5 version), at times, I am experiencing some error messages. These are: Timeout, executable did not return. (code: PE018) DNS could not be resolved Socket Error # 11004 (socket error # 11004) DNS could not be resolved (socket error # 11004)
The one with PE018 in it is related to the http full page sensor. The DNS messages show up on the ping sensor, the TCP connect sensor and the http sensor.
Previous versions did not show these errors.
What could be wrong here?
Grtz - Will
Article Comments
I have tried the fullpage sensor on 2 homepages being http://maasshuttles.nl and http://projena.info. I'm experiencing the same issue with both.
The DNS message is not specific enough. It might be that the DNS server itself could not be resolved. Which seems somewhat strange because it is pointing to the IP adresses of the DNS-servers of the ISP. Or it might be that the DNS servers of the ISP could not resolve the domain name. Which seems also strange since everything works fine when starting the browser on the same system where PRTG resides.
Either way, DNS problem also happens occasionally - say 3-5 times every 24 hours when using a test interval of 10 minutes. Additionally, I tried with 3 sensors - TCP connect, ping and http. The issue occurred in all 3 cases.
I never experienced this in the previous version (i.e. some 9.1.5 release).
Dec, 2011 - Permalink
Hello,
we do see the same issues when monitoring those two sites with HTTP Full Page Sensors:
RESOURCE NOT FOUND http projena.info/
RESOURCE NOT FOUND http maasshuttles.nl/
or
-2146697208 http maasshuttles.nl/
so this rather seems to be an issue on the websites than in PRTG.
Dec, 2011 - Permalink
Do you see them permanent? Or every once and a while?
The message you are showing are 'http projena.info/'. Shouldn't that be 'http://projena.info'?
Dec, 2011 - Permalink
We only see the errors every now and then. The responses are missing a few characters but the sensors are targeting the correct pages.
Dec, 2011 - Permalink
Could it be that the error message is related to an exceeded timeout? In other words, when a web page takes to long to complete, the treshold is exceeded. And instead of showing a nice timeout message stating that the pageload did not complete within the specified amount of time, some error handling kicks-in showing something strange about an executable that did not complete.
I did some more investigation by fiddling around with the thresholds. And with lower settings, the message comes more often than with higher settings. In fact, when set to one second, the error is always there.
Dec, 2011 - Permalink
You are right, the error - message is actually a timeout and should say that. We'll change this.
Jan, 2012 - Permalink
For troubleshooting could you please tell us which website you monitor with the HTTP Fullpage sensor? Does the error occur on every HTTP Fullpage Sensor or only on some of them?
As to the other sensors, which DNS could not be resolved. Is it a public one?
Dec, 2011 - Permalink