Does anyone know whether 'Timeout' parameter in the agent configuration file limits the execution time of active checks, as well as passive?
We're moving from 1.4.x to 2.0.0 agents on some hosts, and previously we've thought that active checks were able to run longer than this timeout allowed, unlike passive checks. This seemed to be case with the 1.4.x agent, but with the 2.0.0 agent active checks which take a while to execute seem to fail (appearing as 'not supported' on the server) unless we increase the 'Timeout' value.
We're moving from 1.4.x to 2.0.0 agents on some hosts, and previously we've thought that active checks were able to run longer than this timeout allowed, unlike passive checks. This seemed to be case with the 1.4.x agent, but with the 2.0.0 agent active checks which take a while to execute seem to fail (appearing as 'not supported' on the server) unless we increase the 'Timeout' value.
Comment