MySQL Bugs: #76487: mysqld.log filling with messages during Zabbix transactions.

Bug #76487	mysqld.log filling with messages during Zabbix transactions.
Submitted:	25 Mar 2015 20:21	Modified:	26 Apr 2015 17:30
Reporter:	Jeffrey Simonson	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.1.69	OS:	Linux (CentOS 6.4)
Assigned to:		CPU Architecture:	Any
Tags:	mysqld.log zabbix

Description:
InnoDB: clust index record PHYSICAL RECORD: n_fields 7; compact format; info bits 0
 0: len 6; hex 0000066f445e; asc    oD^;; 1: len 6; hex 000001a743cb; asc     C ;; 2: le
n 7; hex 800000002d0476; asc     - v;; 3: len 8; hex 00000000000069ac; asc       i ;; 4:
 len 4; hex d501ed8f; asc     ;; 5: len 8; hex 0000000000000193; asc         ;; 6: len 4
; hex 9f36533f; asc  6S?;;

TRANSACTION 0 37820647, ACTIVE 0 sec, process no 1336, OS thread id 140110570673920 star
ting index read, thread declared inside InnoDB 500
mysql tables in use 1, locked 0
5 lock struct(s), heap size 1216, 1 row lock(s), undo log entries 187
MySQL thread id 29, query id 9121 localhost zabbix Sending data
select clock,ns,value from history_uint where itemid=25830 and clock>1427314230 and cloc
k<=1427314233

InnoDB: Submit a detailed bug report to http://bugs.mysql.com

How to repeat:
Unknown Steps to Reproduce.  

This database is used for Zabbix.  Some recent change in Zabbix might have started causing this error.  mysqld.log gets so many messages, it files the /var volume and stops Zabbix.

What version of MySQL is this?  If it is anything less than 5.6.23, please consider upgrading, and then if messages continue, try rebuilding the affected tables:   ALTER TABLE <table> FORCE, ALGORITHM=COPY;   and see if that helps.

I see I had the wrong MySQL version listed.  It is actually 5.1.69.

"mysql  Ver 14.14 Distrib 5.1.69, for redhat-linux-gnu (x86_64) using readline 5.1"

I'll accept Shane's advice to upgrade to 5.6.23 or newer.  Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".