I was looking in my RT log file for a different issue and found the following.
eval {…} called at -e line 0 (/usr/local/share/perl5/Carp.pm:169)
[3523] [Thu Dec 4 18:24:43 2014] [critical]: Attachment insert failed: Row size
too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=D
YNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of
768 bytes is stored inline. (/opt/rt-4.2.6/sbin/…/lib/RT/Attachment.pm:221)
[3523] [Thu Dec 4 18:24:43 2014] [critical]: Attachment insert failed: Row size
too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=D
YNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of
768 bytes is stored inline. (/opt/rt-4.2.6/sbin/…/lib/RT/Attachment.pm:191)
I thought I raised the attachment size limit when I installed RT. Do I need to do that again? We provide a few specialized, internal services and our customers insist on emailing us super giant attachments.
I was looking in my RT log file for a different issue and found the
following [snip]
I thought I raised the attachment size limit when I installed RT. Do I
need to do that again? We provide a few specialized, internal services
and our customers insist on emailing us super giant attachments.
This is caused by changes in MySQL 5.6 (see the first IMPORTANT CHANGE):
Thus, in addition to setting max_allowed_packet, you will need to
increase innodb_log_file_size, or you’ll only be able to insert files
which are < 5M (or, on 5.6.22 or higher, < 10M). Note that increasing
innodb_log_file_size is slightly complex:
Thus, in addition to setting max_allowed_packet, you will need to
increase innodb_log_file_size, or you’ll only be able to insert files
which are < 5M (or, on 5.6.22 or higher, < 10M). Note that increasing
innodb_log_file_size is slightly complex: