Hi,
I am getting a lot of errors like this in my zabbix_server.log:
034431:20060517:223206 Expression [({12439}>89)&({12440}<96)] cannot be evaluated [Unable to get value for functionid [12439]]
Well, I recognize [({12439}>89)&({12440}<96)] as one of my trigger expressions:
({Host.Unix:fs.root.pct.last(0)}>89)&({Host.Unix:f s.root.pct.last(0)}>96)
Here is what mysql has for that functionid...
mysql> select * from functions where functionid=12439\G;
*************************** 1. row ***************************
functionid: 12439
itemid: 18630
triggerid: 12823
lastvalue: NULL
function: last
parameter: 0
Why does it think it can't evaluate the expression? I have verified that the trigger actually works: if I modify the expression and change 89 to 9, the trigger turns on. It's weird too because I have a similar trigger expression but with >79 in the first part and <90 in the second part and this version is not producing errors.
Also, I tried simplifying the expression to ({Host.Unix:fs.root.pct.last(0)}>89) but it produces the same error. I do have two sepparate triggers with this type of expression defined, but only one of them generates the error - which is just weird.
Anybody have any insight?
Thanks
Daniel
I am getting a lot of errors like this in my zabbix_server.log:
034431:20060517:223206 Expression [({12439}>89)&({12440}<96)] cannot be evaluated [Unable to get value for functionid [12439]]
Well, I recognize [({12439}>89)&({12440}<96)] as one of my trigger expressions:
({Host.Unix:fs.root.pct.last(0)}>89)&({Host.Unix:f s.root.pct.last(0)}>96)
Here is what mysql has for that functionid...
mysql> select * from functions where functionid=12439\G;
*************************** 1. row ***************************
functionid: 12439
itemid: 18630
triggerid: 12823
lastvalue: NULL
function: last
parameter: 0
Why does it think it can't evaluate the expression? I have verified that the trigger actually works: if I modify the expression and change 89 to 9, the trigger turns on. It's weird too because I have a similar trigger expression but with >79 in the first part and <90 in the second part and this version is not producing errors.
Also, I tried simplifying the expression to ({Host.Unix:fs.root.pct.last(0)}>89) but it produces the same error. I do have two sepparate triggers with this type of expression defined, but only one of them generates the error - which is just weird.
Anybody have any insight?
Thanks
Daniel
Comment