Hi guys and girls,
could everyone report which database version is your Zimbra9 running ? there seems to be a glitch in the database versioning scheme.
I got some up to date zimbra9 running in version 111, and some others in 112.
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."
it would be nice to report here after your current version, if your zimbra is up to date.
regards.
I've been using the Zextras build for years and the output of your command is:
PERL_USE_UNSAFE_INC=1 perl -MMigrate -e "Migrate::verifySchemaVersion(111)" Mon Feb 19 14:30:31 2024: Schema version mismatch. Expected version 111. Version in the database is 112
hi phoenix, thanks for your reply.
Version 112 confirm there is a glitch in the versioning scheme build by zextras.
Same here
Wed Mar 20 20:25:19 2024: Schema version mismatch. Expected version 111. Version in the database is 112.
@donty thanks.
Version 112 confirm there is a glitch in the versioning scheme build by zextras.
could you specify OS distrib/version (Centos 7/RHEL 8/almalinux 8 ...)
Ubuntu 18.04.6 on ESM. Be good to get a reliable upgrade. We have a enough users for a failure to be a long problem and enough data to take a lot of time to move it about.
Would love to get things on a better footing away from an old OS and unpatched stuff but now getting to the point when the effort is possibly best spent dropping it.
I suspect as a plan we may move to Carbonio in the next little while as things are just too precarious and lumpy to stay with Zimbra. Just really fed up some of the major FOSS/OSS projects are adopting the Enshi*tification process so enthusiastically. I've been using Zimbra since 2005 in one form or another and found the way the commercial interests worked have always been a thorn in the better adoption or wider investment. I just don't trust Zimbra to maintain an open source option at all.
I think Zextras Carbonio is a better route but I am not clear about the basis upon which their model works to support the project into the future.
Isn't life simple 😉
Hi, I had the same problem. It was caused by migrate20210506-BriefcaseApi.pl, a file in /opt/zimbra/libexec/scripts that shouldn't be there.
(See https://forums.zimbra.org/viewtopic.php?p=312270&sid=ba209dd318336e5ce11d731477776b80#p312270)
Later, I made a build with P40 from https://github.com/zimbra/zm-build#building and it would not start zmmailboxd. The error was:
2024-09-08 18:55:39,480 ERROR [main] [] Versions - DB Version Mismatch: ours=111 from DB=112
2024-09-08 18:55:39,480 FATAL [main] [] system - Data version mismatch. Reinitialize or upgrade the backend data store.
So, I did this:
su - zimbra
cd /opt/zimbra/libexec/scripts
PERL_USE_UNSAFE_INC=1 perl -MMigrate -e "Migrate::updateSchemaVersion(112, 111);"
This downgraded the version number in the database from 112 to 111, which it should have been anyway.
I don't know if this was stupid or dangerous, but it worked.