Help, i made the update to 10.1.13 ubuntu 20

[alextr]

Ok after 2 weeks of going back and forth with support ( btw super slow), the only solution is to reinstall zimbra.

[alextr]

Ok, back online. Everything is working now after I reinstalled zimbra all settings made are still there.

[scantec]

Wow, that's sad to know that support was not able to help you fix a problem created by an update!

Ok after 2 weeks of going back and forth with support ( btw super slow), the only solution is to reinstall zimbra.

[Martinwiertz]

Ok, back online. Everything is working now after I reinstalled zimbra all settings made are still there.

Please explain what you did to fix the problem. Reinstall but what version?
I am stuck on 10.1.10 Foss and it looks like a Jetty issue based on Some Posts. Updating as Intalio suggests will result in zmmailbox not starting.

I am not clear what to do. 24 zimbra patches are waiting to upgrade to 1.13 and 1.15.

[adrian.gibanel.btactic]

Ok, back online. Everything is working now after I reinstalled zimbra all settings made are still there.

Please explain what you did to fix the problem. Reinstall but what version?

Please notice that @alextr is using a Network Edition version and not a FOSS build.

I am stuck on 10.1.10 Foss and it looks like a Jetty issue based on Some Posts. Updating as Intalio suggests will result in zmmailbox not starting.

I am not clear what to do. 24 zimbra patches are waiting to upgrade to 10.1.13 and 10.1.15.

If you are willing to upgrade with whatever Intalio publish in their repos you can:
- Either apply a workaround consisting on downgrading jetty.
- Or apply a workaround changing some configuration files manually.
Assuming you can revert to a previous VPS snapshot that's what I would do.

Or wait till mid 2026 January where some of these commits embargo might end. That means all of those embargoed commits would appear at once in the mid 2026 January Intalio update with whatever it's also released in that mid 2026 January release by Zimbra themselves (or part of it if there's another embargo).

[Martinwiertz]

Ok, back online. Everything is working now after I reinstalled zimbra all settings made are still there.

Please explain what you did to fix the problem. Reinstall but what version?

Please notice that @alextr is using a Network Edition version and not a FOSS build.

I am stuck on 10.1.10 Foss and it looks like a Jetty issue based on Some Posts. Updating as Intalio suggests will result in zmmailbox not starting.

I am not clear what to do. 24 zimbra patches are waiting to upgrade to 10.1.13 and 10.1.15.

If you are willing to upgrade with whatever Intalio publish in their repos you can:
- Either apply a workaround consisting on downgrading jetty.
- Or apply a workaround changing some configuration files manually.
Assuming you can revert to a previous VPS snapshot that's what I would do.

Or wait till mid 2026 January where some of these commits embargo might end. That means all of those embargoed commits would appear at once in the mid 2026 January Intalio update with whatever it's also released in that mid 2026 January release by Zimbra themselves (or part of it if there's another embargo).

Thanks, I am going to try the tips! Always able to revert to a backup.
Waiting until January is an option but I don't know if this will be the solution. Intalio provides 10.1.15 upgrade via apt update &&upgrade already but isn't working. I'll test and find out.

I appreciate your help and in general your active support on the forum.

[Martinwiertz]

Hi,

Update:
full backup of server
install all patches from Zimbra
reboot
Zimbra not running - mailbox service
apt install zimbra-jetty-distribution=9.4.46.v20220331-2.u22
restart services
all services running

zmcontrol -v
Release 10.1.14.INTALIO.20250425.UBUNTU22_64 FOSS edition.

Thanks!

Zimbra patches installed:
zimbra-clamav-db/unknown 1.0.0-1zimbra8.7b3.22.04 all [upgradable from: 1.0.0-1zimbra8.7b2.22.04]
zimbra-clamav-lib/unknown 1.4.3-1zimbra8.8b4.22.04 amd64 [upgradable from: 1.0.8-1zimbra8.8b4.22.04]
zimbra-clamav/unknown 1.4.3-1zimbra8.8b4.22.04 amd64 [upgradable from: 1.0.8-1zimbra8.8b4.22.04]
zimbra-common-core-jar/unknown 10.1.13.1761912123-1.u22 amd64 [upgradable from: 10.1.10.1751349175-1.u22]
zimbra-common-core-libs/unknown 10.1.15.1762779814-1.u22 amd64 [upgradable from: 10.1.4.1732820104-1.u22]
zimbra-common-mbox-conf-attrs/unknown 10.1.13.1760357419-1.u22 amd64 [upgradable from: 10.1.10.1751289315-1.u22]
zimbra-common-mbox-conf-msgs/unknown 10.1.13.1760016439-1.u22 amd64 [upgradable from: 10.1.10.1751348793-1.u22]
zimbra-core-components/unknown 10.1.5-1zimbra10.0b1.22.04 all [upgradable from: 10.1.3-1zimbra10.0b1.22.04]
zimbra-jetty-distribution/unknown,unknown 9.4.57.v20241219-2.u22 amd64 [upgradable from: 9.4.46.v20220331-2.u22]
zimbra-ldap-components/unknown 10.1.2-1zimbra10.0b1.22.04 all [upgradable from: 10.1.0-1zimbra10.0b1.22.04]
zimbra-ldap-patch/unknown 10.intalio.1.14.u22 amd64 [upgradable from: 10.intalio.1.10.u22]
zimbra-mbox-admin-console-war/unknown 10.1.13.1759852961-1.u22 amd64 [upgradable from: 10.1.10.1751279184-1.u22]
zimbra-mbox-store-libs/unknown 10.1.15.1762779814-1.u22 amd64 [upgradable from: 10.1.4.1732820104-1.u22]
zimbra-mbox-war/unknown 10.1.14.1762779151-1.u22 amd64 [upgradable from: 10.1.0.1720592346-1.u22]
zimbra-mbox-webclient-war/unknown 10.1.14.1762780126-1.u22 amd64 [upgradable from: 10.1.10.1751290195-1.u22]
zimbra-mta-components/unknown 10.1.4-1zimbra8.8b1.22.04 all [upgradable from: 10.1.2-1zimbra8.8b1.22.04]
zimbra-mta-patch/unknown 10.intalio.1.14.u22 amd64 [upgradable from: 10.intalio.1.10.u22]
zimbra-openssl-lib/unknown 3.5.1-1zimbra8.8b1.22.04 amd64 [upgradable from: 3.0.9-1zimbra8.8b1.22.04]
zimbra-openssl/unknown 3.5.1-1zimbra8.8b1.22.04 amd64 [upgradable from: 3.0.9-1zimbra8.8b1.22.04]
zimbra-postfix/unknown 3.6.14-1zimbra8.7b6.22.04 amd64 [upgradable from: 3.6.14-1zimbra8.7b5.22.04]
zimbra-proxy-patch/unknown 10.intalio.1.14.u22 amd64 [upgradable from: 10.intalio.1.12.u22]
zimbra-rsync/unknown 3.4.1-1zimbra8.7b2.22.04 amd64 [upgradable from: 3.4.1-1zimbra8.7b1.22.04]