SQLException: innodb_log_file_size headache
Jonathan Feally <[email protected]> Mon, 21 Mar 2016 02:07:04 -0700
| Newsgroups | gmane.mail.imap.dbmail |
|---|---|
| Message-ID | <[email protected]> |
FYI, After performing a number of upgrades on my FreeBSD ports based install on an older release of FreeBSD 9.1-STABLE, I started getting corrupt messages. Since it was seemingly random on message with attachments, and I had upgraded postfix, mailscanner, dbmail, and mysql all the the same time, it took a while before I could capture a queued message. I finally was able to determine that postfix and mailscanner were not to blame, but rather somewhere in dbmail/mysql. After taking a look in lmtp logs I found: Mar 21 01:28:57 mail.consult-sc dbmail-lmtpd[74282]: [0x804c21810] Error:[message] blob_insert(+203): SQLException: The size of BLOB/TEXT data inserted in one transaction is greater than 10% of redo log size. Increase the redo log size using innodb_log_file_size. Here is a link to explain what changed in MySQL: http://dba.stackexchange.com/questions/75328/row-size-error-with-mysql This message is to make sure that nobody else starts to run into this issue. My change to my.cnf: ###innodb_log_file_size=5242880 # Too Small!! innodb_log_file_size=1048576000 # Close to 100MB accepted now which is large enough for most normal email setups -Jon