[Users] DO NOT UPGRADE to 10.0.12 or 10.1.4!

[Randy Leiker]

Hi Frédéric, 

I installed 10.0.12 on one of my Zimbra professional services client's clusters last night and have not seen any issues over the last 14 hours so far. On that cluster, it has two dedicated LDAP servers operating in a MMR configuration. The mailbox stores, MTAs, and proxies are likewise on dedicated hosts. CPU usage trends over the 14 hours so far match the historical baseline usage for those servers. 

With the high CPU usage on your LDAP servers, and the slowness of the services on the mailbox servers, I would initially suspect possible corruption in the LDAP schema or data. My next suspicion would be corrupted data in the mailboxes or their search indexes. For example, it could have been something that affected the on-disk copy of the LDAP data prior to the installation of the patch, but went unnoticed until you restarted the Zimbra services following the installation of the patch. 

One method for determining if there are problems in either the LDAP schema or data is to dump it to text files on your production server, and import it on a test Zimbra server to see if any errors are present. Past experience has taught me that the zmslapcat and zmslapadd utilities will complain if there are problems encountered. Here's a brief outline of the steps: 

On your production server: 


    * mkdir /tmp/ldapdata 
    * cd /tmp/ldapdata 
    * sudo su - zimbra 
    * /opt/zimbra/libexec/zmslapcat -c /tmp/ldapdata 
    * /opt/zimbra/libexec/zmslapcat /tmp/ldapdata 

In a test environment, spin up a temporary server running the same Zimbra version & patch level as your production server, copy the exported LDAP files to your test server in a temporary directory, set the zimbra user as the owner of those files, then: 


    * sudo su - zimbra 
    * zmcontrol stop 
    * cd /opt/zimbra/data/ldap 
    * mv mdb mdb.old 
    * mkdir -p mdb/db 
    * /opt/zimbra/libexec/zmslapadd /path/to/ldap.bak 

Where /path/to/ldap.bak is the location of the exported LDAP files from your production server. If the LDAP data is bad, it will normally report this as errors on the console. Otherwise, if the LDAP data is good, it will import without warnings or errors. If the LDAP data is good, you may want to do a check of all of the MariaDB tables in your mailbox servers, followed by a blob check of the mailboxes. 


Randy Leiker ( randy at skywaynetworks.com ) 
Skyway Networks, LLC 
[ http://www.skywaynetworks.com/ | https://skywaynetworks.com ] 


From: "Frédéric Nass" <frederic.nass at univ-lorraine.fr> 
To: "users" <users at lists.zetalliance.org> 
Sent: Thursday, December 19, 2024 6:20:42 AM 
Subject: [Users] DO NOT UPGRADE to 10.0.12 or 10.1.4! 

Hi, 

The latest Zimbra minor release (at least 10.0.12, and probably alos 10.1.4) is malfunctioning. Among the symptoms observed after updating: abnormal CPU load on zldap, significant slowdowns when starting stores, inaccessible webmail. We are awaiting news from our partners and Zimbra support. 





Do not upgrade to this version! 

Frédéric Nass 

Sous-direction Infrastructures et Services 
Direction du Numérique 
Université de Lorraine 
Tél : +33 3 72 74 11 35 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zetalliance.org/pipermail/users_lists.zetalliance.org/attachments/20241219/6643b662/attachment-0001.html>