<![CDATA[Agent time-out configuration]]>Hello, Victor!

I want to monitor disk queue on remote PC, I've wrote script in bash that returns disk queue, but it takes 5 minutes for this script to return a value ( i used command: iostat -xd /dev/sda 300 2). I've modifed time-out's in nxagentd.conf for server to wait. While it works server keeps asking agent to return a value, in the end i have a plenty of iostat processes running, and no value is returned to server. How can i configure agent/server to wait 5 minutes and take a value from the script?

]]>https://forum.netxms.org/topic/304/agent-time-out-configurationRSS for NodeFri, 13 Nov 2026 09:21:20 GMTThu, 17 Apr 2008 11:53:24 GMT60<![CDATA[Reply to Agent time-out configuration on Thu, 17 Apr 2008 13:22:11 GMT]]>I suggest you to do it that way:

*) add your iostat script to the crontab and redirect it's output so some file
*) change external parameter's command to 'cat /file_with_data'

]]>https://forum.netxms.org/post/1484https://forum.netxms.org/post/1484Thu, 17 Apr 2008 13:22:11 GMT<![CDATA[Reply to Agent time-out configuration on Thu, 17 Apr 2008 13:05:26 GMT]]>I have found AgentCommandTimeout parameter in server configuration. Modifying it to the correct time solves the problem. But now all agents have this big time-out and every other paramter I monitor at this node is now waiting for iostat to recieve a value, is there a way to configure this time-out only for some paramaters, so that others wouldn't wait for it? Any work-around is welcome.

]]>https://forum.netxms.org/post/1479https://forum.netxms.org/post/1479Thu, 17 Apr 2008 13:05:26 GMT