ZBX_NOTSUPPORTED but should be

[ReefShark]

I'm having difficulty with MySQL monitoring on one of my servers. Using the same template and (standard) user-defined checks that work fine on another (MySQL) host, the agent spits out "ZBX_NOTSUPPORTED" errors when (I think) it shouldn't.

The content of the zabbix_agentd.conf is this:
UserParameter=mysql.ping,mysqladmin -uroot  -ppassword ping|grep alive|wc -l
UserParameter=mysql.uptime,mysqladmin -uroot -ppassword status|cut -f2 -d":"|cut -f1 -d"T"
UserParameter=mysql.threads,mysqladmin -uroot -ppassword status|cut -f3 -d":"|cut -f1 -d"Q"
UserParameter=mysql.questions,mysqladmin -uroot -ppassword status|cut -f4 -d":"|cut -f1 -d"S"
UserParameter=mysql.slowqueries,mysqladmin -uroot -ppassword status|cut -f5 -d":"|cut -f1 -d"O"
UserParameter=mysql.qps,mysqladmin -uroot -ppassword status|cut -f9 -d":"
UserParameter=mysql.version,mysql -V

When I run 'zabbix_agentd -p' on the server, the MySQL section is:

mysql.ping                                    [t|1]
mysql.uptime                                  [t| 1712921  ]
mysql.threads                                 [t| 1  ]
mysql.questions                               [t| 1471253  ]
mysql.slowqueries                             [t| 0  ]
mysql.qps                                     [t| 0.859]
mysql.version                                 [t|mysql  Ver 14.12 Distrib 5.0.18, for suse-linux (i686) using readline 5.1]

When I shoot 'zabbix_get' commands at the host from my zabbix server, I get ZBX_NOTSUPPORTED errors:

# zabbix_get -s mysqlhost -k system.uptime
1715014
# zabbix_get -s mysqlhost -k mysql.uptime
ZBX_NOTSUPPORTED
# zabbix_get -s mysqlhost -k mysql.questions
ZBX_NOTSUPPORTED

I'm assuming I'm overlooking something very obvious and very stupid, but I have no idea what it is.
Hope someone can shove me in the right direction...

[Alexei]

I would suggest getting read of spaces after numbers returned by user parameters.

[ReefShark]

I added

|tr -d " "

to all the relevant entries and that solved the problem.

Thanks for the quick reply Alexei.

But I think it would be nice if the MySQL entries in the zabbix_agentd.conf file supplied with Zabbix would be corrected in future releases of Zabbix. First of all, it should contain this 'trailing space fix' and second of all, the name are all wrong (mysql[ping] should be mysql.ping, mysql[uptime] should be mysql.uptime, etc). This will solve a few very silly problems one can encounter with a fresh install or when he/she is new to Zabbix.

[ReefShark]

I do run into another little problem related to these entries.

mysql.ping returns a value of '0' when queried from the zabbix server (also if I use zabbix_get from the zabbix server), but locally (with zabbix_agentd -p) and if I run the command (mysqladmin -uroot -ppassword ping|grep alive|wc -l) on the mysqlhost, it returns '1'. MySQL is up and running fine.

Probably something equally silly as a trailing space in the output, but I've not found the problem here yet either.

[ReefShark]

^bump^

Anyone?

[byronsmith]

^bump^

Anyone?

I too am having this problem!

i.e

ZABBIX SERVER
[root@server-zbx01 zabbix]# zabbix_get -s server-hd01 -p 10050 -k mysql.ping
0

[root@server-zbx01 zabbix]# zabbix_get -s server-hd01 -p 10050 -k mysql.uptime
ZBX_NOTSUPPORTED

ZABBIX AGENT
[root@server-hd01 zabbix]# zabbix_agentd -t mysql.ping
mysql.ping [t|1]

[root@server-hd01 zabbix]# zabbix_agentd -t mysql.uptime
mysql.uptime [t|1674190]

[ReefShark]

^BUMP^

I've not been able to solve the mysql.ping problem, unfortunately. Any advice would be greatly appreciated.

[loophole]

Check the mysql.err log also i'm not quite sure if it stats why a login is not correct.
What I'm thinking of is the permission rights with the mysql server. Check on mysql.user table. See if the user you try to mysql.ping got the right to also connect from diffrent host not only localhost.

Just create a user that has acces from every host like that

Insert Into mysql.user host="%", name="status";

[byronsmith]

Hi

Just to let you know, it was a permission issue. I set "AllowRoot=1" on the Zabbix Agent and all is good. I know it's not good practice to use root but my Zabbix Agent port has restrictions.

Thanks for your help.

Regards
Byron