A year or so ago, I posted how I got Zimbra 4.0.3 mostly stable on Ubuntu 6.06.1 LTS and haven't had anything but minor problems with it since. Lately the spam filter has been showing it's age, so I decided it was time to upgrade.
Everything seemed to be going pretty well, until the database schema upgrade, where it did this:
which is the same error tachijuan
Executing SQL statements in /tmp/migrate-MailboxGroup.sql
mysql invocation failed, exit code = 256: at /opt/zimbra/libexec/scripts/migrate20060911-MailboxGroup.pl line 76,
got when upgrading 4.0.2GA to 4.5.4GA. I never saw a post on solving that issue.
Reading back through my install log (the entirety of which I've attached as a txt file), I see an interesting spot that I didn't notice during the install :
At a guess, I'd say the check table timed out or something, and the Zimbra install didn't see any of the errors it was looking for (maybe "Got error: 2013" didn't fit the case statement? ), and went on it's way.
Verifying integrity of message store databases. This may take a while.
mysqld is alive
/opt/zimbra/mysql/bin/mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'CHECK TABLE ... CHANGED'
No errors found
Is this something anyone else has seen?
Any idea where the "Generating report" line might have stashed such a report?