-
Problem report
-
Resolution: Fixed
-
Major
-
3.4.0
-
Centos 7
-
Sprint 17, Sprint 18
-
1
Since 3.4 exit code for scripts is checked, it means that some scripts will now become unsupported, for example grep:
"Normally the exit status is 0 if a line is selected, 1 if no lines were selected, and 2 if an error occurred."
So it is expected that some commands should not become unsupported on some error codes.
UserParameter examples are also broken.
Current workaround to make default example work is to change following user parameter:
mailq
UserParameter=unix_mail.queue,mailq | grep -v "Mail queue is empty" | grep -c '^[0-9A-Z]'
To:
UserParameter=unix_mail.queue,mailq | grep -v "Mail queue is empty" | grep -c '^[0-9A-Z]' || true
MySQL
UserParameter=mysql.ping,mysqladmin -uroot ping | grep -c alive
To:
UserParameter=mysql.ping,mysqladmin -uroot ping | grep alive | wc -l
- is duplicated by
-
ZBX-12740 Issue with Zabbix agent 3.4 UserParameter: "ZBX_NOTSUPPORTED: 0"
- Closed
- part of
-
ZBXNEXT-1380 Zabbix server should check the return code of media scripts
- Closed