Erro with nodata after migrate from 1.8.2 to 1.8.3

[thiagomz]

Guys,

I am receiving this error after migrate from zabbix 1.8.2 to 1.8.3.

22837:20100816:115331.419 Expression [{16524}=1] cannot be evaluated: Evaluation failed for function: nodata
22837:20100816:115331.439 Evaluation failed for function: nodata
22837:20100816:115331.439 Expression [{13646}=1] cannot be evaluated: Evaluation failed for function: nodata


The expression is it :

{AZ_Oracle_AZMon_Java:oracleexpdp.nodata(93600)}=1

If i do not receive a status from my last oracle backup, it fire a alert for me.

[makini]

We also got those errors after the upgrade to 1.8.3 but for "max" and "last" functions:

Expression [({100100000019744}#{100100000019743})] cannot be evaluated: Evaluation failed for function: max
...
Expression [({100100000023143})#({100100000023144})] cannot be evaluated: Evaluation failed for function: last

What do these mean?

[urkle]

I am encountering this same issue.. (specifically the .nodata() one) as I have several checks that look for nodata against Log files and values pushed by services via the zabbix_sender. This affects 26 fairly high critical alerts.

[urkle]

To the original poster.. I just looked through the source code and the .nodata errors can be ignored when they occur on server startup.

If you look at src/libs/zbxserver/evalfunc.c at line 1353 (in version 1.8.3), you will see a check to NOT fire the trigger if the server has just been started up.

This is relation to this post I believe.
http://www.zabbix.org/forum/showpost.php?p=31738&postcount=3

It's just a BAD error message IMHO.. It should be more specific that "nodata check skipping on server startup" instead.

[jonh]

I am seeing a HUGE number of log messages like the following immediately after upgrading from 1.8.2 to 1.8.3:

24326:20100818:131432.843 Expression [({143249}>{143248})&({143247}=0)] cannot be evaluated: Evaluation failed for function: last

The numbers change but there are already tens of thousands of them in zabbix_server.log after a few minutes of uptime.

[danrog]

I am seeing the same thing with logseverity and last on two different systems (and it seems to happen only on recently created triggers for me).

I think it could be related to triggers on items that haven't received any new data since the upgrade. In my case, I am looking for specific event log messages that haven't come in since the upgrade. Still researching on my side so this is just a guess at this point.

Here is a query simple query to find out what trigger is causing the issue (you can add t.* and f.* to get more info if you want)

SELECT host, t.description, f.triggerid, t.value, i.itemid, i.value_type
FROM triggers t
INNER JOIN functions f ON ( f.triggerid = t.triggerid )
INNER JOIN items i ON ( i.itemid = f.itemid )
INNER JOIN hosts h ON ( i.hostid = h.hostid )
WHERE f.functionid = 'your number here';

[cozmic]

I also get lots of "evaluation failed" errors after upgrading 1.8.2 > 1.8.3:


31376:20100820:144052.816 Expression [{15347}>150000] cannot be evaluated: Evaluation failed for function: delta
31376:20100820:144052.817 Evaluation failed for function: delta


the trigger numbers keep changing and if I lookup the trigger above:
mysql> select description,comments,error from triggers where expression='{15347}>150000';
+-----------------------------------------+----------+---------------------------------------+
| description | comments | error |
+-----------------------------------------+----------+---------------------------------------+
| ifOutOctets17 on {HOSTNAME} is too High | | Evaluation failed for function: delta |
+-----------------------------------------+----------+---------------------------------------+


Is it a bug or how do I fix this?

[thiagomz]

Guys,


Another error :

3167:20100820:162402.278 Expression [{17041}>0] cannot be evaluated: Evaluation failed for function: diff

Alexei ??

[zabbix_zen]

Development team,

any news on this?

[danrog]

I've opened a bug for this. Feel free to add comments.

https://support.zabbix.com/browse/ZBX-2922