New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


No result or error in XML response

Votes:

0

Your Vote:

Up

Down

Hello, I have deployed EXE/Script Advanced sensor on PRTG server. It's run *.bat then Perl script. Everything is working fine, I get the result in the graph view with scanning interval 15min. But every day at 12am script stop working, with status of sensor "Warning" then "Down" and message: No "result" or "error" in XML response. After a while, the sensor goes "UP" and it works fine again until 12am. What could be the problem?

exe-script prtg xml-response

Created on Mar 7, 2018 10:03:29 AM by  dcme (0) 1



5 Replies

Votes:

0

Your Vote:

Up

Down

If you enable the setting to cache the result to disk, you can see the returned data for those midnight scans.

Let me know what the results are from those scans after midnight.

Created on Mar 8, 2018 4:10:27 AM by  Benjamin Day [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Here is result:

Data['blockedsens'].asString := '';
Data['canlinux'].asString := '0';
Data['channelinfos'].asString := '{"2":{"Unit":"oukCustom","CustomUnit":"","ValueLookupName":"","LimitMode":"0","LimitMinError":"","LimitMinWarning":"","LimitMaxError":"","LimitMaxWarning":"256251"},"3":{"Unit":"oukCustom","CustomUnit":"","ValueLookupName":"","LimitMode":"0","LimitMinError":"","LimitMinWarning":"","LimitMaxError":"","LimitMaxWarning":""}}';
Data['channelnames'].asString := 'ALM_SPS1_USCDB'#$D#$A + 
'2'#$D#$A + 
'AST_SPS1_USCDB'#$D#$A + 
'3'#$D#$A + 
'';
Data['checkfailed'].asString := '0';
Data['environment'].asString := '';
Data['exefile'].asString := 'fnr_stat.bat';
Data['exeparams'].asString := '1682984721';
Data['fastcount'].asString := '0';
Data['host'].asString := '192.168.196.227';
Data['hostv6'].asString := '';
Data['inerror'].asString := '0';
Data['interfacenumber'].asString := '';
Data['inum'].asString := '';
Data['ipversion'].asString := '0';
Data['isexesensor'].asString := '1';
Data['lastmsg'].asString := '#P1';
Data['lastuptime'].asString := '0';
Data['linuxlogindomain'].asString := '';
Data['linuxloginpassword'].asString := '***';
Data['monitorchange'].asString := '';
Data['mutexname'].asString := '';
Data['notonpod'].asString := '0';
Data['reboot'].asString := '43162.1823827894';
Data['reqmsginterval'].asString := '900';
Data['resultfile'].asString := 'Result of Sensor 41264.txt';
Data['sensorid'].asString := '41264';
Data['simulate'].asString := '0';
Data['timeout'].asString := '60';
Data['tlsexplicit_default'].asString := '';
Data['tlsexplicit_ftp'].asString := '';
Data['tlsexplicit_imap'].asString := '';
Data['tlsexplicit_pop3'].asString := '';
Data['tlsexplicit_port'].asString := '';
Data['tlsexplicit_smtp'].asString := '';
Data['uptimecount'].asString := '0';
Data['usednstime'].asString := '0';
Data['usewindowsauthentication'].asString := '0';
Data['windowslogindomain'].asString := '';
Data['windowsloginpassword'].asString := '***';
Data['windowsloginusername'].asString := '';
Data['writeresult'].asString := '

Created on Mar 8, 2018 11:38:19 AM by  dcme (0) 1

Last change on Mar 9, 2018 1:13:49 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Ok, now can you send me one where it's working so I can compare the two of them?

Created on Mar 8, 2018 11:20:54 PM by  Benjamin Day [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks for the help, I found out what the problem is. Files from source node, go with a delay of 2 hours and when it's midnight, the script searches for files for a new day, ignoring the folder the previous day

Created on Mar 9, 2018 12:56:19 PM by  dcme (0) 1



Votes:

0

Your Vote:

Up

Down

Excellent! Glad to hear you found the problem!

Created on Mar 10, 2018 6:41:49 AM by  Benjamin Day [Paessler Support]



Please log in or register to enter your reply.


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.