[ZBXNEXT-1897] Return unknown (unsupported) value by external checker using non-zero exit code Created: 2013 Sep 09  Updated: 2015 Mar 13  Resolved: 2015 Mar 13

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: 2.0.8
Fix Version/s: None

Type: New Feature Request Priority: Minor
Reporter: Pavel Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: exitcodes, externalchecks, userparameters
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates ZBXNEXT-540 ZBX_NOTSUPPORTED from external scripts Open

 Description   

Sometimes external checker cannot get item value - host unavailable or something like this.
If item type is character or text the only way to report about unknown value for external script is sleep and wait until server kill it. Any other action will lead zabbix server to accept and process returned value (including empty string). Function zbx_execute() ignores exit code of executed process.
I think more graceful is assume that external checker should return zero retcode in normal case and treat non-zero retcode as fail (as it is for timeout).
Both windows cmd and unix sh return exit code of executed command as their exit code, it's no problem to check retcode from waitpid().



 Comments   
Comment by richlv [ 2013 Sep 10 ]

similar to ZBXNEXT-152

Comment by richlv [ 2014 Apr 12 ]

ZBXNEXT-2203 might allow to provide custom error message

Comment by richlv [ 2015 Mar 13 ]

closing as a duplicate of ZBXNEXT-540

Generated at Fri Apr 19 16:53:31 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.