Fresh install! Release 7.1.4_GA_2555.SLES11_64_20120105094644 SLES11_64 FOSS edition. What we were doing before this error: importing users mailboxes (using the import/export option of users found in preferences). All seem to go ok until we hit an import of 2GB. This took hours but completed. After that, this user could not login using WebUI or email client. The funny thing is ONLY this user was experiencing this problem. The other users could use their email fine. I check the mailbox logs and find:
Code:
2012-01-16 00:30:45,670 WARN [mailboxd.csv] [] DbStats - An error occurred while getting current database stats
com.zimbra.common.service.ServiceException: system failure: SQL: 'SHOW INNODB STATUS'
ExceptionId:mailboxd.csv:1326691845669:74d105cbd71278c9
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
at com.zimbra.cs.db.DbUtil.executeQuery(DbUtil.java:134)
at com.zimbra.cs.db.DbUtil.executeQuery(DbUtil.java:176)
at com.zimbra.cs.db.DbUtil.executeQuery(DbUtil.java:202)
at com.zimbra.cs.db.DbStats.getStatData(DbStats.java:47)
at com.zimbra.common.stats.RealtimeStats.getData(RealtimeStats.java:67)
at com.zimbra.cs.stats.ZimbraPerf$MailboxdStats.getDataLines(ZimbraPerf.java:520)
at com.zimbra.common.stats.StatsDumper.call(StatsDumper.java:110)
at com.zimbra.common.stats.StatsDumper$1.run(StatsDumper.java:79)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown table engine 'InnoDB'
Query being executed when exception was thrown:
SHOW INNODB STATUS
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:409)
at com.mysql.jdbc.Util.getInstance(Util.java:384)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3566)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3498)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1959)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2113)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2568)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2113)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2275)
at com.zimbra.cs.db.DebugPreparedStatement.executeQuery(DebugPreparedStatement.java:156)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at com.zimbra.cs.db.DbUtil.executeQuery(DbUtil.java:130)
... 8 more
This is the first instance of said error in the logs after the import. I google this error and found most seem to apply to ubuntu users, we are using SLES11. I also see where AppArmor may cause the problem (apparmor has the docs, guides, profile editor and utils installed but i don't see the actual app?) and last but not least, someone reported fixing this error by adding a swap partition (we are not using a swap).
The following info is taken while in the "error" state:
Code:
ls -l /opt/zimbra/data/tmp
total 144
-rw-r----- 1 zimbra zimbra 2940 Jan 15 18:40 .swatch_script.1309
-rw-r----- 1 zimbra zimbra 2940 Jan 15 20:28 .swatch_script.3061
-rw-r----- 1 zimbra zimbra 2940 Jan 15 19:37 .swatch_script.32016
-rw-r----- 1 zimbra zimbra 4511 Jan 15 20:28 .swatch_script.4957
drwxr-x--- 2 zimbra zimbra 4096 Jan 15 20:26 antispam-mysql
drwxr-x--- 3 zimbra zimbra 4096 Jan 15 20:29 calcache
-rw-r----- 1 zimbra zimbra 71819 Jan 15 20:27 jffi5500747603473743922.tmp
drwxr-x--- 2 zimbra zimbra 4096 Jan 15 20:28 mysql
drwxr-xr-x 5 zimbra zimbra 4096 Jan 15 18:13 nginx
-rw-r--r-- 1 root root 8211 Jan 15 18:37 syslog-ng.conf.hvec~
drwxr-x--- 2 zimbra zimbra 4096 Jan 15 18:40 uncompressed
drwxr-x--- 2 zimbra zimbra 4096 Jan 15 18:40 upload
-rw-r--r-- 1 zimbra zimbra 210 Jan 16 08:19 zmcontrol.error.zQnzS
-rw-r----- 1 zimbra zimbra 191 Jan 15 19:32 zmcontrol.out.uGs9m
-rw-r----- 1 zimbra zimbra 191 Jan 15 19:25 zmcontrol.out.vbz0M
-rw-r--r-- 1 zimbra zimbra 0 Jan 16 08:19 zmcontrol.status.VJSw5
mail:~ # su - zimbra
zimbra@mail:~> mysql
mysql> show variables like 'have_innodb';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| have_innodb | NO |
+---------------+-------+
1 row in set (0.00 sec)
mysql> show engines \G
*************************** 1. row ***************************
Engine: CSV
Support: YES
Comment: CSV storage engine
Transactions: NO
XA: NO
Savepoints: NO
*************************** 2. row ***************************
Engine: MRG_MYISAM
Support: YES
Comment: Collection of identical MyISAM tables
Transactions: NO
XA: NO
Savepoints: NO
*************************** 3. row ***************************
Engine: MEMORY
Support: YES
Comment: Hash based, stored in memory, useful for temporary tables
Transactions: NO
XA: NO
Savepoints: NO
*************************** 4. row ***************************
Engine: MyISAM
Support: DEFAULT
Comment: Default engine as of MySQL 3.23 with great performance
Transactions: NO
XA: NO
Savepoints: NO
4 rows in set (0.00 sec)
mysql>SHOW INNODB STATUS;
ERROR 1286 (42000): Unknown table engine 'InnoDB'
mysql> quit
cat /opt/zimbra/conf/my.cnf
[mysqld]
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
slow_query_log = 1
slow_query_log_file = /opt/zimbra/log/myslow.log
ignore-builtin-innodb
plugin-load=innodb=ha_innodb_plugin.so;innodb_trx=ha_innodb_plugin.so;innodb_locks=ha_innodb_plugin.so;innodb_lock_waits=ha_innodb_plugin.so;innodb_cmp=ha_innodb_plugin.so;innodb_cmp_reset=ha_innodb_plugin.so;innodb_cmpmem=ha_innodb_plugin.so;innodb_cmpmem_reset=ha_innodb_plugin.so
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 = 1206498508
innodb_log_file_size = 524288000
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 = 30
innodb_flush_method = O_DIRECT
innodb_flush_log_at_trx_commit = 0
max_allowed_packet = 16777216
[mysqld_safe]
err-log = /opt/zimbra/log/mysqld.log
pid-file = /opt/zimbra/db/mysql.pid I would appreciate ANY help.
Bugzilla
Wiki
Source
SQL: 'SHOW INNODB STATUS' Error 
Linear Mode
