Current Known Issues: Difference between revisions

No edit summary
mNo edit summary
Line 4: Line 4:
=Current Known Issues=  
=Current Known Issues=  
{{KB|{{WIP}}|{{ZCS 9.0}}|{{ZCS 8.8}}|}}
{{KB|{{WIP}}|{{ZCS 9.0}}|}}  


Revision as of 15:31, 16 June 2022

Current Known Issues

   KB 24443        Last updated on 2022-06-16  

(0 votes)


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

List of known issues
  • ZBUG-2837 : zmconfigd is failing for ldap-only nodes. Apply the given workaround -

1. On the ldap server wget these two files for the respective versions in /tmp/:


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

/opt/zimbra/common/lib/jylibs/ /opt/zimbra/libexec/zmconfigd

3. Restart zmconfigd

  • ZBUG-2831 : SMTP authentication failure with 2FA application passcode
  • ZBUG-2833 : All Zimlets are disabled from custom COS after redeploying the Zimlets
  • ZBUG-2834 : No INFO logs while redeploying the Zimlets
  • ZBUG-2835 : /var/log/syslog filling after applying the patch 8.8.15 patch 32. This leads to the disk space filling up.
  • 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(
Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.appender.ConsoleAppender$Target
       at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(
       at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(
       at java.base/java.lang.ClassLoader.loadClass(
       ... 1 more 
  • From Kepler-Patch-25 onwards, customers using SSO will need to update zimbraVirtualHostName attribute for the domains. Please refer to the 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/ -> [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: 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