[ZBX-6894] Server/Proxy behavior for stucked external checks Created: 2013 Aug 14 Updated: 2017 May 30 Resolved: 2015 May 19 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Documentation (D) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Iskra Zabbix | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | externalchecks, timeout | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
It is documented (https://www.zabbix.com/documentation/2.0/manual/appendix/config/zabbix_server and similar for proxy), that Timeout settings affects external checks, as well as SNMP or simple checks. But it is not clear, what happens after Timeout expires. My quick look in checks_external.c/execute.c points out that forked process and all it childrens are killed after Timeout. Correct me if I wrong. Anyway, it is worth to explicitly document de-facto behavior in "External checks" chapter. |
| Comments |
| Comment by Martins Valkovskis [ 2015 Apr 15 ] |
|
Added to documentation at https://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/external (also other versions): "In case of a timeout, the item will be marked as unsupported, an according error message will be displayed and the forked process for the script will be killed." RESOLVED. sasha CLOSED |