[ZBX-6615] Error reporting on script execution broken when no output is produced by a script Created: 2013 May 22  Updated: 2017 Sep 15  Resolved: 2017 Sep 15

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G), Frontend (F), Server (S)
Affects Version/s: 2.0.7rc1
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Oleg Ivanivskyi Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: globalscripts
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate

 Description   

When the script does not produce any output the following error message is presented when executing the script:
ERROR: Cannot connect to the trapper port of zabbix server daemon, but it should be available to run the script.

Example of global script (execute on agent):
killall cat 2>&1

Work-around:
killall cat 2>&1
echo Done

Adding a simple echo statement to the script will resolve this.



 Comments   
Comment by richlv [ 2013 May 22 ]

PLEASE READ ALL COMMENTS ABOVE
it involves frontend (several things) and agent

Comment by Oleksii Zagorskyi [ 2013 May 23 ]

Just a note - the error message has been introduced in ZBX-3219.

Comment by Alexander Vladishev [ 2017 Sep 15 ]

Cannot reproduce from version 3.0. I close this issue as "Won't Fix".

Generated at Thu Apr 03 15:12:37 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.