Current Known Issues ZCS9

Revision as of 19:39, 17 June 2022 by Shanxt (talk | contribs)

Current Known Issues

   KB 24444        Last updated on 2022-06-17  

(0 votes)

Current known issues with ZCS 9.0 patch 25

Summary of the issue: zmconfigd is failing for ldap-only nodes.

Bug number: ZBUG-2837

Description: zmconfigd is failing for ldap-only nodes.

Workaround: 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

Summary of the issue: SMTP authentication failure with 2FA application passcode

Bug number: ZBUG-2831

Description: SMTP authentication failure with 2FA application passcode is configured in client like outlook, thunderbird etc.

Workaround: The following workaround can be applied on the affected server.

1. Open /opt/zimbra/jetty_base/etc/ and add below statement on line no 41.

   <Set name="forwardedPortAsAuthority">false</Set>

2. Restart mailbox after this

Summary of the issue: All Zimlets are disabled from custom COS after redeploying the Zimlets

Bug number: ZBUG-2833

Description: When zimlets are redeployed on the server , then zimlets are disabled on the customer COS.

Workaround: Those zimlets can be enabled on the custom COS manually.

Summary of the issue: No INFO logs while redeploying the Zimlets on the server.

Bug number: ZBUG-2834

Description: When a zimlet is deployed on the server, it shows the output but it doesn't show anything on the screen and zimlet gets deployed silently in backend.

Workaround: N/A

Summary of the issue: /var/log/syslog filling after applying the patch-25 on ZCS-9 and this leads to the disk space filling up.

Bug number: ZBUG-2835

Description: /var/log/syslog filling after applying the patch 8.8.15 patch 32. This leads to the disk space filling up.

Workaround: The following workaround can be applied on the affected server.

1. Open /opt/zimbra/conf/ and update line no 195 and change value to info from debug. 2. Update line no 210 and remove SLOGGER from statement. 3. Restart mailbox after this

  • 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
Jump to: navigation, search