Yay.
I looked in mailbox.log and found
Code:
[root@testserver zimbra]# grep config.frm /opt/zimbra/log/mailbox.log
Caused by: java.sql.SQLException: Incorrect information in file: './zimbra/config.frm'
And I then looked in
/opt/zimbra/db/data/`hostname`.err and found many similar errors like this
Code:
080403 13:22:10 [ERROR] /opt/zimbra/mysql/libexec/mysqld: Incorrect information in file: './zimbra/volume.frm'
080403 13:22:24 [ERROR] /opt/zimbra/mysql/libexec/mysqld: Incorrect information in file: './zimbra/config.frm'
Turns out the innodb buffers are set to large for my test machine. The
production machine as 16GB and the test machine has 2GB.
Code:
[zimbra@testserver conf]$ grep size /opt/zimbra/conf/my.cnf
sort_buffer_size = 1048576
read_buffer_size = 1048576
# Increase the size of the table cache, since each mailbox has its
innodb_buffer_pool_size = 5025638400
innodb_log_file_size = 104857600
innodb_log_buffer_size = 8388608
Code:
[zimbra@prodserver conf]$ free
total used free shared buffers cached
Mem: 16359336 16249640 109696 0 335676 7426924
-/+ buffers/cache: 8487040 7872296
Swap: 5261240 5120 5256120 Code:
[zimbra@testserver conf]$ free
total used free shared buffers cached
Mem: 2057292 1472876 584416 0 125600 621432
-/+ buffers/cache: 725844 1331448
Swap: 1052248 51188 1001060 So after turning innodb_buffer_pool_size way down tomcat started and Zimbra
WUI works. Now I'll just have to coax out the appropriate values and continue
with upgrade testing.
I wonder if there is a zimbra tool that comes up with some sane defaults for a given RAM configuration.