External Checks broken after upgrade from 1.8 to 2.0.2

[ucs75]

Last night, I installed a fresh installation of Zabbix 2.0.2 on a Centos 5.8 x64 server. I added the php frontend to an existing web-server, copied my old 1.8 database to a new DB, and ran the update script on it. Then I updated my config files so that each system knew about each other.

At first, it looked good (other than odd periodic messages that the Zabbix Server was not running)

Then I noticed that all my MySQL data was completely broken. The graphs contained blips of data and periods of no data. Further, the blips of data often were WAY out of normal and expected ranges.

Specifically, I have used external checks to monitor the MySQL performance metrics. The excerpt of a config file is here:

UserParameter=mysql.ping,mysqladmin -uroot -h127.0.0.1 ping|grep alive|wc -l
UserParameter=mysql.uptime,mysqladmin -uroot -h127.0.0.1 status|cut -f2 -d":"|cut -f1 -d"T"
UserParameter=mysql.threads,mysqladmin -uroot -h127.0.0.1 status|cut -f3 -d":"|cut -f1 -d"Q"
UserParameter=mysql.questions,mysqladmin -uroot -h127.0.0.1 status|cut -f4 -d":"|cut -f1 -d"S"
UserParameter=mysql.slowqueries,mysqladmin -uroot -h127.0.0.1 status|cut -f5 -d":"|cut -f1 -d"O"
UserParameter=mysql.qps,mysqladmin -uroot -h127.0.0.1 status|cut -f9 -d":"
UserParameter=mysql.version,mysql -V

Now, this has worked flawlessly for months under Zabbix 1.8, and I can execute the statements locally on the monitored host and receive the correct values on every try.

However the zabbix_server.log is showing the following (for example):

 29754:20120830:175643.838 item [FTLX001 - MySQL Server:mysql.questions] became not supported: Type of received value [3122000000000.000000] is not suitable for value type [Numeric (float)]
 29754:20120830:175643.885 item [FTLX001 - MySQL Server:mysql.questions] became supported
 29754:20120830:175643.909 item [FTLX001 - MySQL Server:mysql.questions] became not supported: Type of received value [3231833333333.333496] is not suitable for value type [Numeric (float)]
 29754:20120830:175643.917 item [FTLX001 - MySQL Server:mysql.questions] became supported
 29754:20120830:175643.933 item [FTLX001 - MySQL Server:mysql.questions] became not supported: Type of received value [3140333333333.333496] is not suitable for value type [Numeric (float)]
 29754:20120830:175643.941 item [FTLX001 - MySQL Server:mysql.questions] became supported
 29754:20120830:175643.961 item [FTLX001 - MySQL Server:mysql.questions] became not supported: Type of received value [5297000000000.000000] is not suitable for value type [Numeric (float)]
 29754:20120830:175719.205 item [FTLX001 - MySQL Server:mysql.questions] became supported

It looks like the host is sending back wild numbers, but I don't believe that is possible, since nothing changed on the agent. (I did try using the 2.0 agent as a test -- with no observable change in behavior).

2.0.2 Server seems to be mangling the data to the point of uselessness. Has anyone else experienced this .... or better yet.... found a resolution?!

[ucs75]

Disregard the above....

There was actually a typo in the config file which caused the error in the log. The pasted code did not contain the typo (it came from an identical server that was missing the typo).

the typo was a trailing '.' after the check name.


The checks still don't work using the 2.0 agent, and work fine with the 1.8 agent - but that is an issue for another thread.