"Unable to get value for functionid"

[technow0rker]

Same problem.
Value "lastvalue" (table functions) magically became NULL. Workaround with manually updating MySQL tables fixed that, but I'm interested in investigating the reasons, i.e. why the situation appeared. I made an upgrade of all zabbix agents and server from 1.1.6 to 1.1.7 some time ago. Could this be a reason? Probably not. AFAIK, the problem existed with versions prior to 1.1.6 too. Maybe this is some kind of "feature"? I did not find any comments from developers though.

[bbrendon]

I thought this might go away in the 1.4 series, but I'm still getting it with 1.4.1.

[elgoretto]

"mee-too" + 1 ^^
Had the same issue with a fresh 1.4.2 install.
The SQL command cleaned the upcoming log entries.

[elgoretto]

This weekend the problem showed up again.

It seems like it happened since I started to "play" with SNMP enabled hosts and SNMP auto-discovery, as I didn't see these sort of things in zabbix logs when I had only zabbix agent and simple checks enabled (and ad-hoc auto-discovery of course).

I won't be able to validate Zabbix usage in my infra if the mysql database keeps getting corrupted

I will remove SNMP hosts and discovery SNMP related actions, apply the DB fix again and see what happens.

--
edit:
More about this problem:
One of my 2 SNMP hosts didn't get updated (triggers) when I got "evaluation" erros in logs. As soon as the DB fix is applied, triggers change states (which is coherent).

[Niels]

I'm also seeing this, when I turn on SNMP.

Developers: Can you please acknowledge that you're aware of this problem?

[elgoretto]

I'm also seeing this, when I turn on SNMP.

Developers: Can you please acknowledge that you're aware of this problem?

Thanks for your feedback.
I also note that since my last message in this thread (I disabled SNMP actions on autodiscovery and do not interact with SNMP devices discovered so far), I had no "functionid" problem.
I'll remove one of my SNMP device and reenable SNMP discovery action, and report here if this test is significant. In a second time, I'll do this for all my SNMP devices.

[elgoretto]

I just looked at zabbix server logs again, and waw, that's really fast.
As I said, I reenabled SNMP related actions, and now I get "functionid" errors again.

Could a developper plan to take a look at that, please?

[elgoretto]

A "up" to say that since almost a month without using SNMP autodiscovery, no problem occured.
There seems to be a real problem with that feature.

[elgoretto]

Hi,

It's time for the "up of the month", as there seems to be no mention of this SNMP autodiscovery bug anywhere else in the forum.

Would be useful if users who have the SNMP autodiscovery actually active and running can report if they experience the same DB corruption.
Useful too if some member of the Zabbix crew could at least acknowledge this thread.

[Niels]

Reported as ZBX-178.

[elgoretto]

Thanks Niels.

[CeeEss]

"Unable to get value for functionid" (revisited)

Reported as ZBX-178.

Running a fresh install of 1.4.5 with imported database (mysqldumped from a v1.4.2 installation):

ZABBIX Server (daemon) v1.4.5 (25 March 2008)
Compilation time: Apr 9 2008 13:17:15

Is this related to ZBX-178? Lots of these errors in my zabbix_server.log

3972:20080416:102147 Query failed:You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '???:???' at line 1 [1064]
3972:20080416:102147 No function for functionid:[???:???]
3972:20080416:102147 Expression [{???:???}] cannot be evaluated [Unable to get value for functionid [???:???]]

After enabling query logging, lots of these too:

25 Query select 0,lastvalue from functions where functionid=???:???

Looking back at the server log for the 1.4.2 install, the same errors are there as well.

thanks

- cal

[Alexei]

3972:20080416:102147 Expression [{???:???}] cannot be evaluated [Unable to get value for functionid [???:???]]

You may select all triggers having expression {???:???} directly from ZABBIX database and remove it from ZABBIX GUI. This should help. The problem will be fixed soon.

[MrKen]

This problem persists in Zabbix 1.6

Using the information in this thread I was able to rectify this problem in Zabbix 1.4.2 many months ago. After applying the fix, below, I never had any more problems. In my case this only affected Delta items.

Unfortunately, this problem still exists in Zabbix 1.6. I have today applied the same fix to 1.6 that I applied to 1.4.2 and all seems to be OK.

mysql> alter table functions alter lastvalue set default 0;

[This changed the default value of column 'lastvalue' from NULL to 0]

mysql> update functions set lastvalue=0 where lastvalue is NULL and function='delta';

[This updated the existing values from NULL to 0]


I wonder what happened to ZBX-178 !!!

MrKen

[CeeEss]

Funny, it's gone away in 1.6 on my setup. I'm running the stable 6169 build right now. Well worth getting a very recent build.

- cal