I am not sure a new build will help you. You could try re-cloning, but this may require manual intervention.No joy:I will try re-cloning the original install. Maybe there was an error in the copying. ***Did not work. Looks like I will have to build v10 from scratch.Code:
Restoring existing configuration file from /opt/zimbra/.saveconfig/localconfig.xml...doneOperations logged to /tmp/zmsetup.20231207-080114.logAdding /opt/zimbra/conf/ca/ca.pem to cacertsUpgrading from 9.0.0_ZEXTRAS_20221203 to 10.0.5_GA_1000Stopping zimbra services...done.This appears to be 9.0.0_ZEXTRASStarting mysql...done.Checking ldap status...not running.Checking ldap status...not running.Starting ldap...done.Running mysql_upgrade...done.Schema upgrade required from version 112 to 118.Running /opt/zimbra/libexec/scripts/migrate20200625-MobileDevices.plThu Dec 7 08:01:55 2023: Verified schema version 112.Thu Dec 7 08:01:55 2023: Adding mobile_operator column to ZIMBRA.MOBILE_DEVICES table.ERROR 1060 (42S21) at line 1: Duplicate column name 'mobile_operator'Thu Dec 7 08:01:56 2023: Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=EWaEeScLCHI77RbMxmJ_WuTn2r --database=zimbra --batch --skip-column-names'.Script failed with code 256: - exitingUPGRADE FAILED - exiting.
The migration script from schema version 112 to 113 is failing due to ZIMBRA.MOBILE_DEVICES.mobile_operator already existing, which says to me either:
1) 9.0.0_ZEXTRAS added this column out of sync with the upstream schema, or
2) the schema upgrade script was interrupted in a previous run, having added the column but failing to update the database schema version.
Re-cloning and upgrading again seems like a wise first step. If that fails, check the install log. Finally, I would inspect the upgrade script (/opt/zimbra/libexec/scripts/migrate20200625-MobileDevices.pl) and manually apply the schema changes for 112->113 and then try running again.
Statistics: Posted by jered — Sun Dec 10, 2023 3:34 pm