<![CDATA[[RESOLVED] Nxagent configuration param - ExecTimeout]]>Hi there!

As I understand, this parameter extends execution timeout for queries done locally on monitored server by netxms agent
That`s right?

I have set it to: ExecTimeout=200000
But still have "Cannot get parameter: communication failure" for an ExternalParameter which 100% is working, because:

  1. we use it on a bunch of servers
  2. it is shell script which runs as expected from CMD

I have tried to set it as ExternalParameterShellExec, too. Without any luck

CMD`s output for script:
***@***:~# time /***/report_***_idleness.sh 20 Casino    
OK

real    0m2.513s
user    0m0.000s
sys     0m0.000s

Output shown is definently stdout and "OK" text is expected!

Is ExecTimeout really working parameter?
May be, i need to set some other parameter?

]]>https://forum.netxms.org/topic/810/resolved-nxagent-configuration-param-exectimeoutRSS for NodeFri, 13 Nov 2026 10:05:47 GMTThu, 07 Jan 2010 14:18:12 GMT60<![CDATA[Reply to [RESOLVED] Nxagent configuration param - ExecTimeout on Tue, 12 Jan 2010 13:48:23 GMT]]>Yep!!!

That worked.

little note for every others: for server`s timeout to apply NetXMS server needs to be restarted after change

]]>https://forum.netxms.org/post/3792https://forum.netxms.org/post/3792Tue, 12 Jan 2010 13:48:23 GMT<![CDATA[Reply to [RESOLVED] Nxagent configuration param - ExecTimeout on Thu, 07 Jan 2010 16:15:16 GMT]]>Hello!

In fact, there are two timeouts - one on agent side, for script execution, and one on server side - for agent response to command. If you have external parameters with long execution time, you should also increase value for server's parameter AgentCommandTimeout, which is 2 seconds by default.

Best regards,
Victor

]]>https://forum.netxms.org/post/3780https://forum.netxms.org/post/3780Thu, 07 Jan 2010 16:15:16 GMT