Hi Everyone,

I'm running 7.0 FOSS on Centos 5.5 64bit (4GB RAM) and have run into an odd issue after an upgrade from 6.0.10. This is a very small installation, but with very large mailboxes (~50GB).

This is a single-server installation.

While running imapsync to migrate another mailbox to my ZCS 7 server, I started getting errors about unable to create IMAP folders.

Here's a log snippet when I send an email to the mailbox (from mailbox.log):



2011-02-11 09:15:23,642 INFO [LmtpServer-13796] [name=work@example.net;mid=5;ip=1.2.3.4;] lmtp - try again for message work@example.net: exception occurred
com.zimbra.common.service.ServiceException: system failure: fetching folder data for mailbox 5
ExceptionId:LmtpServer-13796:1297444523642:b80e3d2bc8d5f7fa
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
at com.zimbra.cs.db.DbMailItem.getFoldersAndTags(DbMa ilItem.java:2095)
at com.zimbra.cs.mailbox.Mailbox.loadFoldersAndTags(M ailbox.java:1525)
at com.zimbra.cs.mailbox.Mailbox.beginTransaction(Mai lbox.java:1230)
at com.zimbra.cs.mailbox.Mailbox.beginTransaction(Mai lbox.java:1177)
at com.zimbra.cs.mailbox.Mailbox.getItemById(Mailbox. java:2044)
at com.zimbra.cs.mailbox.Mailbox.getFolderById(Mailbo x.java:2935)
at com.zimbra.cs.filter.IncomingMessageHandler.getDef aultFolderPath(IncomingMessageHandler.java:76)
at com.zimbra.cs.filter.RuleManager.applyRulesToIncom ingMessage(RuleManager.java:406)
at com.zimbra.cs.filter.RuleManager.applyRulesToIncom ingMessage(RuleManager.java:363)
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver MessageToLocalMailboxes(ZimbraLmtpBackend.java:524 )
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver (ZimbraLmtpBackend.java:336)
at com.zimbra.cs.lmtpserver.LmtpHandler.processMessag eData(LmtpHandler.java:371)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.continueDA TA(TcpLmtpHandler.java:74)
at com.zimbra.cs.lmtpserver.LmtpHandler.doDATA(LmtpHa ndler.java:356)
at com.zimbra.cs.lmtpserver.LmtpHandler.processComman d(LmtpHandler.java:172)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.processCom mand(TcpLmtpHandler.java:66)
at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHandler.java:196)
at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:139)
at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorEx ception: Unknown table engine 'InnoDB5?4'

Query being executed when exception was thrown:
SELECT mi.id, mi.type, mi.parent_id, mi.folder_id, mi.index_id, mi.imap_id, mi.date, mi.size, mi.volume_id, mi.blob_digest, mi.unread, mi.flags, mi.tags, mi.subject, mi.name, mi.metadata, mi.mod_metadata, mi.change_date, mi.mod_content FROM mboxgroup5.mail_item AS mi WHERE mailbox_id = 5 AND type IN (1,2,13,3)


Any suggestions?

Here's ~zimbra/conf/my.cnf:
====================

[mysqld]

slow_query_log_file = /opt/zimbra/log/myslow.log

slow_query_log = 1

plugin-load = innodb=ha_innodb_plugin.so;innodb_trx=ha_innodb_pl ugin.so;innodb_locks=ha_innodb_plugin.so;innodb_lo ck_waits=ha_innodb_plugin.so;innodb_cmp=ha_innodb_ plugin.so;innodb_cmp_reset=ha_innodb_plugin.so;inn odb_cmpmem=ha_innodb_plugin.so;innodb_cmpmem_reset =ha_innodb_plugin.so

ignore-builtin-innodb
;JB;innodb_force_recovery = 1


basedir = /opt/zimbra/mysql
datadir = /opt/zimbra/db/data
socket = /opt/zimbra/db/mysql.sock
pid-file = /opt/zimbra/db/mysql.pid
bind-address = localhost
port = 7306
user = zimbra
tmpdir = /opt/zimbra/data/tmp

external-locking

long-query-time = 1
log-queries-not-using-indexes

thread_cache_size = 110
max_connections = 110

# We do a lot of writes, query cache turns out to be not useful.
query_cache_type = 0

sort_buffer_size = 1048576
read_buffer_size = 1048576

# (Num mailbox groups * Num tables in each group) + padding
table_cache = 1200

innodb_buffer_pool_size = 1242461798
innodb_log_file_size = 104857600
innodb_log_buffer_size = 8388608
innodb_file_per_table

# Value is: 200 + max_connections + 2 * table_cache
innodb_open_files = 2710

innodb_max_dirty_pages_pct = 10
innodb_flush_method = O_DIRECT
innodb_flush_log_at_trx_commit = 0

[mysqld_safe]

err-log = /opt/zimbra/log/mysqld.log
pid-file = /opt/zimbra/db/mysql.pid