[ZBX-700] Server crash when using {TRIGGER.NAME} for notifications Created: 2009 Feb 12 Updated: 2017 May 30 Resolved: 2009 Feb 12 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 1.6 |
Fix Version/s: | 1.6 |
Type: | Incident report | Priority: | Major |
Reporter: | Alexander Vladishev | Assignee: | Alexander Vladishev |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
3855:20090211:011607 Conditions match our event. Execute operation. 3855:20090211:011607 In substitute_simple_macros (data:"{TRIGGER.NAME} : {STATUS}")3855:20090211:011607 Before replace_to [{] 3855:20090211:011607 In substitute_simple_macros (data:"Processor load is too high on {HOSTNAME}") 3855:20090211:011607 Query [select expression from triggers where triggerid=13409] 3855:20090211:011607 End substitute_simple_macros (result:<90>Y{L^^?) 3855:20090211:011607 After replace_to [<90>^Y{L^^^?] 3855:20090211:011607 End substitute_simple_macros (result:<90>Y{L^^?: PROBLEM) 3855:20090211:011607 End substitute_macros(result:<90>Y{L^^?: PROBLEM) 3855:20090211:011607 In substitute_macros(data:"{TRIGGER.NAME}: {STATUS} ") : {STATUS}") ") |
Comments |
Comment by richlv [ 2009 Sep 15 ] |
closing all resolved issues |