---

Subject:	Happens to me too! But,
Author:	[Not Specified]
Posted:	2014-10-01 14:03

Happens to me too! But, having 3 systems with mysql being monitored, only one of them gives this error...weird...

---

Subject:	What version of
Author:	Jay Stanley
Posted:	2014-10-02 15:04

What version of PythonCollector and mySQL ZenPack I would make sure you are up to date on both.

http://wiki.zenoss.org/ZenPack:PythonCollector
http://wiki.zenoss.org/ZenPack:MySQL_Database_Monitor_(Core)

---

Subject:	once you update both, you may
Author:	Andrew Kirch
Posted:	2014-10-02 15:37

once you update both, you may want to do a zenmodel/zencommand run on the device giving the error, pastebin the output and link it here.

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard

---

Subject:	Might be related to this bug
Author:	Jay Stanley
Posted:	2014-10-02 19:10

Might be related to this bug too
https://github.com/zenoss/ZenPacks.zenoss.PythonCollector/commit/9e10f6d...

---

Subject:	Hi, I just updated both
Author:	Joan
Posted:	2015-02-25 11:03

Hi, I just updated both zenpython and mysql and still getting the error on one of the hosts. Could you fix it

---

Subject:	run zenmodel/zencommand with
Author:	Andrew Kirch
Posted:	2015-02-26 13:36

run zenpython run -v10 -d deviceid and pastebin the output please

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard

---

Subject:	I'm seeing the same thing on
Author:	Daniel Rich
Posted:	2015-03-02 16:37

I'm seeing the same thing on two of my MySQL servers, with plenty of other servers not showing any errors. The only thing I can see with the two servers that are throwing the error is that they are both MySQL 5.0. Most of my others are 5.3+.

The error is very frequent and never advances beyond a count of 1. The event doesn't include a stack trace, just the eventKey of mysql_result and the message of "tuple index out of range". To give an example of how frequent, I currently see 1123 rows of events for one of the hosts in the past 24 hours, consisting entirely of "tuple index out of range" followed shortly by "Monitoring ok". I am seeing both Sev Critical and Sev Error events as well.

---

Subject:	By special request, here's a
Author:	Daniel Rich
Posted:	2015-03-02 16:40

By special request, here's a pastebin of the zenpython command Andrew asked for above.

http://pastebin.com/yKyC1hP1

---

Subject:	In talking to whfsdude and
Author:	Daniel Rich
Posted:	2015-03-02 17:45

In talking to whfsdude and jstanley on IRC, it looks like the ZenPack my require that you grant the PROCESS role to whatever user you are using. So you will need to run the following in mysql on your database server:
GRANT SELECT, SUPER, PROCESS, REPLICATION CLIENT ON *.* to username'@'%' IDENTIFIED BY 'password';
(or you can replace the % with the FQDN of your zenoss server if you want to limit access.

I'm going to let this sit over night to see if the errors stop and if I start getting data in my MySQL graphs.

---

Subject:	Adding cluther to the mix on
Author:	Daniel Rich
Posted:	2015-03-03 11:18

Adding cluther to the mix on IRC this morning we managed to find the problem, there is now a defect open for it (ZEN-16928). I added a patch to the case, I can't add it here since there doesn't seem to be a way to put code into a forum post that doesn't completely fubar the formatting. The problem should only occur on Mysql 5.0 (and possibly 5.1, I don't have one to test with). It's because "SHOW ENGINE INNODB STATUS" and "SHOW SLAVE STATUS" return a different number of columns in older MySQL versions.