Server/Agentd Timeout Parameter in config

[cardelli]

Could you give some more information on Timeout value for server and/or agentd operations ?

In zabbix_server.conf we get:
# Specifies how long we wait for agent (in sec)
# Must be between 1 and 30
Timeout=3

What happens if i set to 10 seconds, does it affect all operations or just the slow responding agent ? I use to check special dynamic web pages via local (server) agent and sometime they can be slow but always interesting to me.

The agent is on the server itself and checks an URL passed via the parameter [], the agentd itself has the timeout to a maximum of 10 seconds. Is this affecting the single request or the agent.

Thank you for your time.

[James Wells]

Greetings,

From what I have been able to determine the timeout setting changes how long the agent will wait for the results of a single check, for the agent and a single agent query for the server. So if you change the agent to have a 10 second timeout, it will wait for up to 10 seconds for each test it performs. This can be both good and bad obviously, but if you are fairly confident of your systems performance, you should be able to change these values as you see fit.

Please note that this timeout means that the agent / server thread child that is performing these tests will be unavailable for up to {timeout} seconds, and as such may cause other tests to fail, get missed, or delayed

[cardelli]

Do you mean that in any case the thread will wait the answer (for example) 10 seconds ? Or maybe the server thread will wait the answer for a maximum amount of 10 seconds, what if i get the answer in just 1 second ?

Thank you for your reply.

[James Wells]

Do you mean that in any case the thread will wait the answer (for example) 10 seconds ? Or maybe the server thread will wait the answer for a maximum amount of 10 seconds, what if i get the answer in just 1 second ?

Thank you for your reply.

Guess I wasn't clear enough... Sorry.

It will wait till it recieves an answer or, in your case, up to 10 seconds which ever comes first. So the thread will move to the next test immediately upon recieving an answer, or if it doesn't, as soon as it reaches the timeout value.