Zimbra 10.1.16 Released - Please Post Your Patch/Upgrade Results Here

[btrent98]

That was it! I spoke to the person who applied the patch and she did stop the services before applying. We ran the script to update the ldap schema and backups are working again.

Makes me wonder though if anything else was impacted by the fact the patch was applied with the services stopped. Any thoughts?

Thanks to all who helped with this.

[rainer_d]

I was under the impression that everything has to always run when patching?

[Martinwiertz]

Upgrade went well. System (FOSS) was running while upgrading. (full backup performed prior)

[BradC]

I was under the impression that everything has to always run when patching?

That's the way we've always done it. In reality though, you probably only need ldap and mysql running.

[yeak]

Upgraded to 10.1.16 successfully. Discover PDF file preview in Modern UI is partially broken. Once zoom in the file, cannot zoom back. Have to reload the browser. Also see Administrators forum for others who reported the same.

[yeak]

In Modern UI press Ctrl-P bring up browser print view with content. After upgraded to 10.1.16, print view shows blank content.

Workaround is to use ... to choose Print menu.

So integration of Ctrl-P to print is broken.

[adrian.gibanel.btactic]

Code: Select all

root@newzmoby:~# su - zimbra
zimbra@newzmoby:~$ zmprov gs $(zmhostname) zimbraBackupDeduplication
# name newzmoby.atcorp.com

zimbra@newzmoby:~$ zmprov gs $(zmhostname) zimbraBackupDedupeCompressionType
# name newzmoby.atcorp.com

zimbra@newzmoby:~$ zmprov gs $(zmhostname) zimbraBackupCSDReset             
# name newzmoby.atcorp.com

zimbra@newzmoby:~$ dpkg -l | grep zimbra-ldap-patch
ii  zimbra-ldap-patch                          10.1.16.1767758060-1.u20                                            amd64        Zimbra ldap Patch
zimbra@newzmoby:~$ dpkg -l | grep zimbra-patch
ii  zimbra-patch                               10.1.16.1770142646-2.u20                                            amd64        Zimbra Network Patch

For whatever reason, it looks like we don't have any of those 3 config variables defined?

We had the same problem.

The error:

ERROR: account.INVALID_ATTR_NAME (invalid attr name: invalid attr name - unable to modify attributes: ldap host=<hostname>.com:389: zimbraBackupDeduplication: attribute type undefined)

means that the zimbraBackupDeduplication attribute is missing from the zimbra schema.

It is missing because the LDAP server update was most likely performed with Zimbra services turned off.

With services turned off, the LDAP schema zimbra.ldif is not updated.

To resolve the issue:
we ran the following script: /opt/zimbra/lib/patches/ldap/ldap_schema_upgrade.sh
and after zmcontrol restart, this updates the Zimbra schema.

Remember to always take a snapshot of the VM first.

Best regards

So... in one Ubuntu 22.04 cluster everything went ok.
In another Ubuntu 22.04 cluster ( ZCS NE 10.1.15 to ZCS NE 10.1.16 ) somehow the dist-upgrade process did not update the ldap schema.

Running zmbackup manually did not output any problem but backups were not being done any more.
Using zmbackup --debug unveiled this problem:

Code: Select all

Error occurred: Cannot invoke "String.equals(Object)" because the return value of "com.zimbra.cs.account.Server.getAttr(String)" is null
java.lang.NullPointerException: Cannot invoke "String.equals(Object)" because the return value of "com.zimbra.cs.account.Server.getAttr(String)" is null
at com.zimbra.cs.backup.BackupUtil.main(BackupUtil.java:143)

Trying to set zimbraBackupDeduplication ended on an:

Code: Select all

ERROR: account.INVALID_ATTR_NAME (invalid attr name: invalid attr name - unable to modify attributes: ldap host=<hostname>.com:389: zimbraBackupDeduplication: attribute type undefined)

error.

Running: /opt/zimbra/lib/patches/ldap/ldap_schema_upgrade.sh in the ldap node fixed the issue.

So... what's new in our case it's that both ldap and mailboxes nodes were up and running when the upgrade (apt-get dist-upgrade) was done (As you expected... ldap node was dist-upgraded first and then mailbox node was dist-upgraded second).

Not sure what might trigger this issue (ldap schema not being upgraded properly) in some Ubuntu 22.04 clusters and not triggering it in other Ubuntu 22.04 clusters.