Bug #68619 InnoDB: Warning: purge reached the head of the history list but its length is...
Submitted: 9 Mar 2013 21:59 Modified: 1 Dec 2013 19:01
Reporter: Jim Ockers Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.1.67 OS:Linux
Assigned to: CPU Architecture:Any
Tags: crash

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[22 Mar 2013 19:58] Jim Ockers
/var/log/messages-20130310 (grep -v [nagios|freshclam|clamd] to remove cruft)

Attachment: messages-20130310 (application/octet-stream, text), 63.97 KiB.

[22 Mar 2013 20:02] Jim Ockers
/var/log/yum.log

Attachment: yum.log (application/octet-stream, text), 29.45 KiB.

[22 Mar 2013 20:03] Jim Ockers
/etc/my.cnf

Attachment: my.cnf (application/octet-stream, text), 275 bytes.

[22 Mar 2013 20:08] Jim Ockers
/var/log/maillog shows Zarafa errors trying to connect to MySQL

Attachment: maillog-20130310 (application/octet-stream, text), 91.00 KiB.

[22 Mar 2013 20:09] Jim Ockers
/var/log/mysqld.log

Attachment: mysqld.log (application/octet-stream, text), 323.68 KiB.

[22 Mar 2013 20:10] Jim Ockers
/etc/init.d/mysqld Red Hat service control for MySQL

Attachment: mysqld (application/octet-stream, text), 5.50 KiB.