I have Zimbra on Rocky 8.10 and it works perfectly. But then the situation is different from yours, since yours came from CentOS and ended up broken due to some dependency issue I don’t have with my installation.
Zimbra supports both RHEL and Rocky, they even provide official paid versions for it.
Note that there is no CentOS 8.x download available, so that would clearly show that CentOS is unsupported.
Your dependency issue is due to unstable OS upgrade. Normally to fix a broken Zimbra installation or when migrating from one system to another, you do something like:
./install.sh -s
which installs Zimbra without configuring it (on whatever OS you are going to use, eg: Rocky or Debian). It’s important at that moment that the version you install is the same as your broken installation. Then you copy/restore your Zimbra data to /opt/zimbra. At this point you can then do:
./install.sh
to get it to run a pseudo upgrade to get your data back and Zimbra running. There’s plenty of cases on the Zimbra forums or also on the internet with that procedure. It’s usually used to move from one OS to the other. Eg: when I moved an installation from Ubuntu to RHEL. Or back when I was using Zimbra 6 and moved it from Debian to Ubuntu when Debian became unsupported.
If you are going to copy it back to the system, then there are LDAP sparse files that you can’t just copy. ZImbra’s documentation has specific rsync commands to do this correctly.
Carbonio is based on Zimbra, so it’s pretty much the same. I got bored of managing and maintaining my own personal email server and migrated to a paid service where I pay effectively 1 euro a month for a 10gb mailbox, and have all my domains connected to it. Since I only had a server with 5 mailboxes and a load of aliases, it made sense to do that than waste my time managing a server and upgrading it, etc. I no longer have to worry about that, and just get on with using email and that’s it.
Yeah 8.8.15 assuming it’s that version is really old. I doubt very much you are going to get that upgraded now, since Zimbra officially stopped providing the OSE/FOSS version a year or two back. Rocky was supported officially from either 9.x or 10.x I can’t remember which one. But people who build the OSE/FOSS version themselves (like myself) got it patched and built before Zimbra offered it. Purely because Rocky is effectively RHEL so you can use the RHEL builds on it.
Zimbra then added to their zm-build scripts on github support for building Rocky. Although those of us that were building it ourselves patched their scripts and built it anyway before the official support was added.
You would need to get 8.8.15 working again before you could even think of upgrading it. And since it would require upgrading to 9.x or 10.0 first it’s going to be near impossible unless you can find those builds available. If you have the package downloaded from when you installed/upgraded Zimbra initially, so the tar.gz of Zimbra 8.8.15 then you’ll be able to fix it. Otherwise, it’s going to be pretty much impossible. Even Zimbra don’t have it in their archive, only 9.x and that is the Network Edition (paid).
Zimbra 8 hasn’t been supported for at least 3 years if not more.
I’ve got the tgz of the 8.8.15 OSE Zimbra no problem…
Currently I am kind of toying with installing CentOS 8 again then reinstalling Zimbra then somehow migrating away… (if I am ever able to fix the MySQL tables within Zimbra)
That’s why I was thinking about Carbonio…
If it can be installed on Say Rocky 9 and is Open Source and active
I dunno about Carbonio, never used it. But you can ask on their forums.
First though, you need to get your existing 8.8.15 sane by doing the things I mentioned above which is the install with the -s parameter to get the packages installed and inplace and all registered with the system permission wise. Then after that, put your data over the top of it and re-run install normally to get your data active. After that you can look at migration once it’s all running stable depending on what options are available.
Worst case, if the Zimbra Admin panel has the migration tool still there, you should be able to sync it across to another Zimbra install on a second server. Or Carbonio.
Or even more worst case, use the console imapsync tool, to migrate the mailboxes to something else entirely. I used that to migrate all my mail to the paid service that I’m now using.
Operations logged to /tmp/install.log.08oDBUPo
Checking for existing installation…
zimbra-drive…NOT FOUND
zimbra-imapd…NOT FOUND
zimbra-patch…NOT FOUND
zimbra-mta-patch…NOT FOUND
zimbra-proxy-patch…NOT FOUND
zimbra-license-tools…NOT FOUND
zimbra-license-extension…NOT FOUND
zimbra-network-store…NOT FOUND
zimbra-network-modules-ng…NOT FOUND
zimbra-chat…NOT FOUND
zimbra-talk…NOT FOUND
zimbra-ldap…NOT FOUND
zimbra-logger…NOT FOUND
zimbra-mta…NOT FOUND
zimbra-dnscache…NOT FOUND
zimbra-snmp…NOT FOUND
zimbra-store…NOT FOUND
zimbra-apache…NOT FOUND
zimbra-spell…NOT FOUND
zimbra-convertd…NOT FOUND
zimbra-memcached…NOT FOUND
zimbra-proxy…NOT FOUND
zimbra-archiving…NOT FOUND
zimbra-core…NOT FOUND
PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE SOFTWARE.
SYNACOR, INC. (“SYNACOR”) WILL ONLY LICENSE THIS SOFTWARE TO YOU IF YOU
FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY DOWNLOADING OR INSTALLING
THE SOFTWARE, OR USING THE PRODUCT, YOU ARE CONSENTING TO BE BOUND BY
THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS
AGREEMENT, THEN DO NOT DOWNLOAD, INSTALL OR USE THE PRODUCT.
License Terms for this Zimbra Collaboration Suite Software:
should help you find out what dependency you are missing. But Zimbra 8.8.15 was only supported on RHEL7 or CentOS 7 so doubt very much you’ll get it working on Rocky 8. You will have to get it working again on RHEL7 or CentOS 7 before you can even think about migrating. And you should be upgrading it on RHEL7 to a newer version before then attempting to migrate to RHEL8 or Rocky8. But that is a Zimbra issue, nothing to do with Rocky. You can’t expect an older Zimbra version to work on Rocky 8 or even RHEL8.
Yeah that should work then. The real question is for which minor release of RHEL8. Because it could be anywhere between 8.0 and 8.10. I couldn’t remember what releases Zimbra 8 supported, especially since nothing is available to download for it now.
I expect the issues you are having is when 8.10 is installed, and it was made for a prior minor release. Instead of Zimbra building it for the major release of a package, it probably got built for the minor, this making it more difficult to run it on 8.10.
Ideally it would be better to ask on the Zimbra forums for assistance in how to get that working again.
But yeah no print available, which means that was a specific dependency for Zimbra 8. Maybe available in an earlier RHEL release, but I’m not sure. Certainly not now anyway. Incidently also not available on my RHEL8 system either.
The above is Zimbra 10, so just showing it does work, but as for Zimbra 8, well not sure what to offer on that. Hope you get it worked out.
Could be problems with /etc/os-release. The post above had the same issue, so if something doesn’t match for the platform it’s expecting, then it’s not going to install.
Obviously since Zimbra 8.8.15 didn’t support Rocky 8, but did support RHEL8, you could substitute the content in /etc/os-release and put RHEL8 data to fool it.
If you wanted to do something like that, then take a copy of /etc/os-release and /etc/redhat-release so that you can revert later. Then put in those files the below:
root@rhel8:~# cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="8.10 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.10"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.10 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8"
BUG_REPORT_URL="https://issues.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.10
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.10"
and:
root@rhel8:~# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.10 (Ootpa)
you could also play with variations by replacing 8.10 with an earlier number until it works. Then get upgraded from Zimbra 8 to 10 and then revert the files.
The lack of the print command would suggest that it’s not recognising the distro, and thus failing to run the install.sh.
Yep it won’t because Rocky wasn’t available back then, nor supported until Zimbra 9 or 10.
Only a problem for Zimbra when you revert it and still on Zimbra 8. Once upgraded to Zimbra 9 or 10 you can revert the files. The files are owned by rocky-release package, so you can also reinstall that package and it should revert them as well.
Yes, so you can symlink it to something else temporarily, or replace the symlink in /etc/os-release with a file instead. Then put the symlink back later once on Zimbra 9 or 10. Or as mentioned if you don’t have them backed up, reinstall rocky-release to reset them. If you end up with os-release.rpmnew instead, then you can just rename that to the os-release file and it will then be OK.
Well, assuming you first did the install.sh -s command to just install Zimbra but not configure it, since this will create all the users that Zimbra requires. Then zmfixperms will work. If you restore your Zimbra directory before running the install command, then the users won’t exist, and it won’t reset the permissions correctly. So you need to do:
install.sh -s
restore your /opt/zimbra directory
install.sh
zimfixperms -verbose -extended
