mikec24 wrote: ↑Tue Jan 20, 2026 4:08 pm
Current: 8.8.15 on Ubuntu VPS (Production)
Upgrade: 10.1.10 on Ubuntu 22.04 (Sandboxed)
Any reason why you haven't upgraded directly to 10.1.15.p1 version?
The only reason is that, 10.1.10 is shown as stable and I wanted the assurance that I could configure and migrate historical data to relatively recent build.
Is there a list of improvements between 10.1.10 and 10.1.15? I could also look at an upgrade to 10.1.15 from 10.1.10 as I have noticed an earlier post, that reports no issues in doing that
I just tried to upgrade Zimbra (running ./install.sh from unpacked installer directory) and get an error from mysql part. Server is latest Ubuntu 22.04.5 LTS.
...
Restoring existing configuration file from /opt/zimbra/.saveconfig/localconfig.xml...done
Copying /tmp/install.log.XJKWgSQZ to /opt/zimbra/log
Operations logged to /tmp/zmsetup.20260122-204648.log
Adding /opt/zimbra/conf/ca/ca.pem to cacerts
Upgrading from 10.1.10_GA_4200003 to 10.1.15_GA_4200001
Stopping zimbra services...done.
This appears to be 10.1.10_GA
Starting mysql...done.
Checking ldap status...not running.
Checking ldap status...not running.
Starting ldap...done.
Running mysql_upgrade...done.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/data/tmp/mysql/mysql.sock' (111 "Connection refused")
Thu Jan 22 20:47:57 2026: Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=[REDACTED] --database=zimbra --batch --skip-column-names'
When I check process list mysql is running and I can connect to it by running command: /opt/zimbra/bin/mysql.
mikec24 wrote: ↑Tue Jan 20, 2026 4:08 pm
Current: 8.8.15 on Ubuntu VPS (Production)
Upgrade: 10.1.10 on Ubuntu 22.04 (Sandboxed)
Any reason why you haven't upgraded directly to 10.1.15.p1 version?
The only reason is that, 10.1.10 is shown as stable and I wanted the assurance that I could configure and migrate historical data to relatively recent build.
Is there a list of improvements between 10.1.10 and 10.1.15? I could also look at an upgrade to 10.1.15 from 10.1.10 as I have noticed an earlier post, that reports no issues in doing that
Sorry, I thought I had seen 10.1.0, not 10.1.10.
Well, even if 10.1.15.p1 is not stable you should be using that because of security reasons. You can check the Network Edition release notes from the different 10.1.10, 10.1.11,... 10.1.15 to check the different changes.
I just tried to upgrade Zimbra (running ./install.sh from unpacked installer directory) and get an error from mysql part. Server is latest Ubuntu 22.04.5 LTS.
...
Restoring existing configuration file from /opt/zimbra/.saveconfig/localconfig.xml...done
Copying /tmp/install.log.XJKWgSQZ to /opt/zimbra/log
Operations logged to /tmp/zmsetup.20260122-204648.log
Adding /opt/zimbra/conf/ca/ca.pem to cacerts
Upgrading from 10.1.10_GA_4200003 to 10.1.15_GA_4200001
Stopping zimbra services...done.
This appears to be 10.1.10_GA
Starting mysql...done.
Checking ldap status...not running.
Checking ldap status...not running.
Starting ldap...done.
Running mysql_upgrade...done.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/zimbra/data/tmp/mysql/mysql.sock' (111 "Connection refused")
Thu Jan 22 20:47:57 2026: Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=[REDACTED] --database=zimbra --batch --skip-column-names'
When I check process list mysql is running and I can connect to it by running command: /opt/zimbra/bin/mysql.
error: Failed dependencies:
zimbra-jetty-distribution >= 9.4.57.v20241219-2.r7 is needed by zimbra-store-10.1.15_GA_4200001.RHEL7_64-20260123182817.x86_64
Setting up zimbra-mbox-store-libs (10.1.15.1762779814-1.u20) ...
dpkg: dependency problems prevent configuration of zimbra-store:
zimbra-store depends on zimbra-jetty-distribution (>= 9.4.57.v20241219-2.u20); however:
Version of zimbra-jetty-distribution on system is 9.4.46.v20220331-2.u20.
Validating ldap configuration
connect: No such file or directory at bin/zmValidateLdap.pl line 159, <DATA> line 755.
Error: Unable to bind to the LDAP server as the root LDAP user.
This is required to upgrade.
This is caused by an empty localconfig.xml. Which I always save before an upgrade so I copied that back and restarted install.sh.
Unfortunately, the installer removes the Jetty Distribution and installs the old version again.