Wanted to post this as a bug report as I've validated on my dev and production ZBX systems.
In my zabbix 3.2 environment, we place our alert scripts in /usr/lib/zabbix/alertscripts
root@null:/usr/lib/zabbix/alertscripts# ls -l /usr/lib/zabbix/
total 8
drwxr-xr-x 2 root root 4096 Nov 13 15:06 alertscripts
drwxr-xr-x 2 root root 4096 Sep 26 10:55 externalscripts
Our Zabbix Server confs call out this dir:
AlertScriptsPath=/usr/lib/zabbix/alertscripts
After upgrading to 3.4.3, I've noticed this variable is ignored and zabbix only looks for scripts in {datadir} which in my (and I imagine most cases) is /usr/share/zabbix/alertscripts/.
I believe the AlertScriptPath parameter is being mishandled or is ignored.
In my zabbix 3.2 environment, we place our alert scripts in /usr/lib/zabbix/alertscripts
root@null:/usr/lib/zabbix/alertscripts# ls -l /usr/lib/zabbix/
total 8
drwxr-xr-x 2 root root 4096 Nov 13 15:06 alertscripts
drwxr-xr-x 2 root root 4096 Sep 26 10:55 externalscripts
Our Zabbix Server confs call out this dir:
AlertScriptsPath=/usr/lib/zabbix/alertscripts
After upgrading to 3.4.3, I've noticed this variable is ignored and zabbix only looks for scripts in {datadir} which in my (and I imagine most cases) is /usr/share/zabbix/alertscripts/.
I believe the AlertScriptPath parameter is being mishandled or is ignored.
Comment