Handling external scripts that sometimes exceed 30 seconds timeout

[mattykay]

Hi all,

Does anyone have any suggestions getting around the maximum 30 second "timeout" Zabbix server/proxy config value?

Having a problem that due to network latency, a PowerShell external script run on a Zabbix proxy sometimes exceeds 30 seconds (usually takes 20s) and seems to get killed by Zabbix, meaning it doesn't get cleaned up leaving a large number of files under /tmp (as per attached link).

Possible Solution:
* Re-write script to be cron-jobbed with using Zabbix-trapper items instead of external scripts. (but this is more hacky than I would like)
* ??

Any ideas? - is >30seconds timeout config possible?

[Atsushi]

It is very difficult to extend the process of getting values from Zabbix server to more than 30 seconds.
As you write, for processing that takes more than 30 seconds, use the periodic execution mechanism such as cron to notify the Zabbix server with the zabbix_sender command. It is also conceivable to output the processing result to a file and let the Zabbix server refer to that file.

[mattykay]

Good points, thanks Atsushi.