I cleaned up the database errors by using mysql creating the mailbox192 database and the tombstone table and then dropping them. Once the InnoDB data dictionary agreed with Zimbra that the user in question was gone, no more errors were displayed at mysql startup.
This time, the upgrade process ran very smoothly (install log attached), with no errors right up to the point it fails with the message:
Tue Feb 26 20:07:52 2008: Verified schema version 27.
Executing SQL statements in /tmp/migrate-MailboxGroup.sql
mysql invocation failed, exit code = 256: at /opt/zimbra/libexec/scripts/migrate20060911-MailboxGroup.pl line 76,
There are no longer any errors in /opt/zimbra/db/data/(hostname).err
Looking at migrate20060911.out.16161, the last command is
080226 20:07:26 mysqld started
080226 20:07:26 [Warning] Changed limits: max_open_files: 1024 max_connections: 16 table_cache: 499
080226 20:07:26 InnoDB: Started; log sequence number 1 3509669002
080226 20:07:26 [Note] /opt/zimbra/mysql/libexec/mysqld: ready for connections.
Version: '5.0.45-log' socket: '/opt/zimbra/db/mysql.sock' port: 7306 Source distribution
Where is it getting that? The mailbox192 database doesn't exist, mysql doesn't think it exists, Zimbra thinks the associated user's account was deleted. Why is it trying to migrate a mailbox that doesn't exist?
192, id, type, parent_id, folder_id, index_id, imap_id,
date, size, volume_id, blob_digest, unread, flags, tags, sender,
subject, metadata, mod_metadata, change_date, mod_content
INTO OUTFILE '/tmp/migrate20060911-16161-mbox192-mail_item.dat'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' LINES TERMINATED BY '\n'
This is starting to get...interesting. In the Chinese curse sense of the word.