[ZBX-23010] Scripts that are links under AlertScriptsPath do not work anymore Created: 2023 Jun 22  Updated: 2024 Nov 19  Resolved: 2024 Sep 29

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D), Server (S)
Affects Version/s: 5.0.35
Fix Version/s: 7.0.5rc1, 7.2.0alpha1

Type: Problem report Priority: Major
Reporter: NAT Helpdesk Assignee: Andris Zeila
Resolution: Fixed Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File ZBX-23010.diff     PNG File image-1.png     PNG File image-2023-06-22-11-18-12-651.png     PNG File image.png    
Issue Links:
Duplicate
Team: Team A
Sprint: S24-W34/35, S24-W38/39
Story Points: 0.5

 Description   

We updated our Zabbix server from version 5.0.31 to 5.0.35 and since then scripts that are links under AlertScriptsPath do not work anymore.
With and till version 5.0.31 we always used links under /usr/lib/zabbix/alertscripts/ without any issue!
Screenshot of the error message:

To workaround this issue we replaced our symbolic links under /usr/lib/zabbix/alertscripts/ with real files!
Maybe this issue has something to do with (ZBX-22688).

 Comments   
Comment by Mark Moses [ 2024 Mar 21 ]

I'm seeing the same behaviour with version 6.0.25

Comment by Vladislavs Sokurenko [ 2024 Apr 10 ]

Thank you for your report, does specifying AlertScriptsPath=/opt help ?

Comment by NAT Helpdesk [ 2024 Apr 10 ]

Maybe yes, but we are still using the described workaround with version 6.0.27 and we can life with it.
I hope the reason for using symbolic links in this case is clear and therefore changing the path for "AlertScriptsPath" does not really reflect that!
In general our hope was that this bug will be quickly fixed with our report, but to our surprise till today it seems to be not fixed.

Comment by Vladislavs Sokurenko [ 2024 Apr 10 ]

This described behaviour has been caused by ZBX-22622 but it was never documented that scripts outside of AlertScriptsPath can be used, unfortunately allowing to execute any script in system is a potential security issue.

Comment by NAT Helpdesk [ 2024 Apr 12 ]

It was possible and therefore we used symbolic links under /usr/lib/zabbix/alertscripts/ because it's a very practical.
I do not share our security concerns.
But we can life with this restriction.

Comment by mason [ 2024 Jun 24 ]

as this is not yet marked as resolved, perhaps another option, configure the server conf file parameters to accept comma (or other character) separated paths for scripts:
AlertScriptsPath
ExternalScripts

this would keep with security (no symlinks) and give us additional options

Comment by Andris Zeila [ 2024 Sep 26 ]

Released ZBX-23010 in:

  • pre-7.0.5rc1 e5ce98c2047
  • pre-7.2.0alpha1 85c56c04130
Generated at Wed Apr 01 10:38:53 EEST 2026 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.