Current Known Issues

Revision as of 15:20, 16 June 2022 by Ashah (talk | contribs)

Current Known Issues


   KB 24443        Last updated on 2022-06-16  




0.00
(0 votes)


Problem

Here is a list of known issues with the current patch release ZCS 8.8.15 patch 32

List of known issues
  • zmconfigd failing on the ldap node after updating to the latest patch
1. On the ldap server wget these two files for the respective versions in /tmp/:

8.8.15.p32
https://raw.githubusercontent.com/Zimbra/zm-core-utils/8.8.15.p32/src/libexec/zmconfigd
https://raw.githubusercontent.com/Zimbra/zm-jython/8.8.15.p32/jylibs/commands.py

2. Take a backup and replace the files in this location:

/opt/zimbra/common/lib/jylibs/commands.py
/opt/zimbra/libexec/zmconfigd

3. Restart zmconfigd 


While deploying zimlets, if the following error is encountered, refer to the patch installation section to install the zimbra-common-core-jar, zimbra-common-core-libs, zimbra-mbox-store-libs packages in a particular order and re-deploy the zimlets

/opt/zimbra/bin/zmjava: line 59: /bin/java: No such file or directory
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/appender/ConsoleAppender$Target
       at com.zimbra.cs.localconfig.LocalConfigCLI.main(LocalConfigCLI.java:353)
Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.appender.ConsoleAppender$Target
       at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:602)
       at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
       at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
       ... 1 more 

From Kepler-Patch-25 onwards, customers using SSO will need to update zimbraVirtualHostName attribute for the domains. Refer to the given instructions to update the attribute

With OpenJDK 17, weaker Kerberos encryption types like 3DES and RC4 have now been disabled by default. This can cause SPNEGO auth to fail if described encryption types are being used. We recommend using stronger encryption types like AES256.

To get SPNEGO auth working with weak encryption types, weak encryption can be enabled by setting the allow_weak_crypto property to true in the krb5.conf configuration file. Please follow below instructions:

1. In /opt/zimbra/jetty_base/etc/krb5.ini.in -> [libdefaults] section, set allow_weak_crypto = true

2. Restart mailboxd service:

su - zimbra
zmmailboxdctl restart


Verified Against: ZCS 8.8 Date Created: 2022-06-16
Article ID: https://wiki.zimbra.com/index.php?title=Current_Known_Issues Date Modified: 2022-06-16



Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »


Jump to: navigation, search