<![CDATA[ServiceCheck.HTTP issue]]>Hi

Our Linux hosting server hanged recently (extremely rare), however I did not receive any alarms for the ServiceCheck.HTTP that was configured for it.

Today I looked further into it... I’ve set a ServiceCheck.HTTP to monitor a web site (apache) on my machine. When I stop the web daemon, the DCI threshold triggers as expected. However, if I disconnect the server from the network no triggering occurs. Is this by design or is this a bug?

Regards,

Dan

]]>https://forum.netxms.org/topic/1563/servicecheck.http-issueRSS for NodeFri, 13 Nov 2026 12:51:17 GMTMon, 16 Jan 2012 11:15:58 GMT60<![CDATA[Reply to ServiceCheck.HTTP issue on Tue, 17 Jan 2012 13:29:26 GMT]]>Hi!

No one complaining so far 🙂 I agree that this is a flaw in default configuration. I'll change default values of AgentCommandTimeout and portcheck timeout.

Best regards,
Victor

]]>https://forum.netxms.org/post/6772https://forum.netxms.org/post/6772Tue, 17 Jan 2012 13:29:26 GMT<![CDATA[Reply to ServiceCheck.HTTP issue on Tue, 17 Jan 2012 11:32:13 GMT]]>Hi Victor,

Thanks for the prompt reply.

I changed the following:

  • server configuration variable AgentCommandTimeout set to 5000;
  • added the following to nxagentd.conf:
            *portCheck
            Timeout = 4000
    The above solved the issue – thank you. So no bug, but is this by design? My settings before the change (I believe them to be the default) where 2 seconds on the server and 30 second on the portCheck agent. Do these not cause issues for other users?

Kind regards,
Dan

]]>https://forum.netxms.org/post/6770https://forum.netxms.org/post/6770Tue, 17 Jan 2012 11:32:13 GMT<![CDATA[Reply to ServiceCheck.HTTP issue on Mon, 16 Jan 2012 11:58:48 GMT]]>Hi!

Could be either a bug or configuration problem. I suppose that TCP connection timeout (for agent to web server connection) is longer than server timeout for agent communication, and so server just didn't wait long enough to get value for ServiceCheck.HTTP parameter, and because there was no new value, threshold was not triggered. I suggest to 1) specify reasonable but short connection timeout in ServiceCheck.HTTP parameter; 2) ad additional threshold for data collection error.

Best regards,
Victor

]]>https://forum.netxms.org/post/6765https://forum.netxms.org/post/6765Mon, 16 Jan 2012 11:58:48 GMT