Hello,
I'm currently experiencing some issues while updating my mail server from 8.8.15 to 9.0.0. I encountered the following error:
Schema upgrade required from version 111 to 118.
Running /opt/zimbra/libexec/scripts/migrate20210506-BriefcaseApi.pl
Mon Nov 6 15:37:33 2023: Verified schema version 111.
Mon Nov 6 15:39:56 2023: Verified schema version 111.
Mon Nov 6 15:39:56 2023: Updating DB schema version from 111 to 112.
ERROR 1036 (HY000) at line 1: Table 'config' is read only
Mon Nov 6 15:39:57 2023: Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=PASSWORD --database=zimbra --batch --skip-column-names'.
Script failed with code 256: - exiting
UPGRADE FAILED - exiting.
I noticed that some others have posted the same error before, but I couldn't find a solution. If anyone has resolved this problem and can offer assistance, I would greatly appreciate it.
I am trying to update it on Ubuntu 18.04.6 LTS
Hi Ahmed,
We can understand your situation. But in your case, there are quite a few complexities.
1. Your host OS is 18.04LTS, a little bit old
2. Updating Zimbra from one version to another, especially on an old OS, is always tricky and full of surprises.
3. The roadmap of Zimbra 9 is yet not so firm.
Considering these facts, we would recommend the following:
1. Install a newer version of the host OS, possibly 20.04LTS, as almost all support it.
2. Configure a fresh email system (we would recommend Carbonio CE), but it's up to your preference; keep the facts of Zimbra 9 in mind.
3. Migrate the system and data from the old server to the new server.
We think this would be the best course of action for you.
We hope it helps. All the best 😊
Have a good day.
Thanks and regards,
Sharif
Hello,
I'm currently experiencing some issues while updating my mail server from 8.8.15 to 9.0.0. I encountered the following error:
Schema upgrade required from version 111 to 118.
Running /opt/zimbra/libexec/scripts/migrate20210506-BriefcaseApi.pl
Mon Nov 6 15:37:33 2023: Verified schema version 111.
Mon Nov 6 15:39:56 2023: Verified schema version 111.
Mon Nov 6 15:39:56 2023: Updating DB schema version from 111 to 112.
ERROR 1036 (HY000) at line 1: Table 'config' is read only
Mon Nov 6 15:39:57 2023: Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=PASSWORD --database=zimbra --batch --skip-column-names'.
Script failed with code 256: - exiting
UPGRADE FAILED - exiting.I noticed that some others have posted the same error before, but I couldn't find a solution. If anyone has resolved this problem and can offer assistance, I would greatly appreciate it.
I am trying to update it on Ubuntu 18.04.6 LTS
Check your database permissions. None of your perms should be set to SELECT only.
I've same kind of problem
ugrading 8.8.15 to zimbra9 on RHEL8
Upgrading from 8.8.15_GA_3953 to 9.0.0_ZEXTRAS_20231104
Stopping zimbra services...done.
This appears to be 8.8.15_GA
Starting mysql...done.
Checking ldap status...not running.
Checking ldap status...not running.
Starting ldap...done.
Running mysql_upgrade...done.
Schema upgrade required from version 111 to 112.
Can't run /opt/zimbra/libexec/scripts/migrate20210506-BriefcaseApi.pl - not executable!
UPGRADE FAILED - exiting.
any help or direction appreciated.
the file is missing and it looks its may be a Z10 file ... so better not use it if its present... see last post here https://forums.zimbra.org/viewtopic.php?t=72475
seems to be mandatory to migrate.
because without it migration process do not validate db version as 112.
So I got it from zimbra github zm-db-conf. then upgrade went fine. but it's not clear to me if it's good practice or not.
OK, your Attention Zextras's people pls.
there seems to be a derive in one recent version of zextras9 build by zextras.
all my VM installed with Zimbra9 by ZEXTRAS and up to date are in database version 112. except some that were not upgraded soon (before Nov 2023)
where all my VM installed in build from other like Ian Walker or Jan Skolnik (sorry if I mispell) are in database version 111. (and up to date)
it is easy to verify with a simple command line
su - zimbra
cd /opt/zimbra/libexec/scripts/
PERL_USE_UNSAFE_INC=1 perl -MMigrate -e "Migrate::verifySchemaVersion(111)"
the output will either be "Wed Feb 14 01:48:14 2024: Verified schema version 111."
or "Wed Feb 14 01:51:08 2024: Schema version mismatch. Expected version 111. Version in the database is 112."
regarding to ZIMBRA post https://forums.zimbra.org/viewtopic.php?p=312270&sid=ba209dd318336e5ce11d731477776b80#p312270
from a zimbra employe there should be no version 112 in any zimbra9.
So this is worrying. for example it prohibits to upgrade from another package builder, not fun, specially if a news security issu arise and zextras took month to fix.