Current Known Issues ZCS9: Difference between revisions
No edit summary |
No edit summary |
||
(18 intermediate revisions by 5 users not shown) | |||
Line 2: | Line 2: | ||
__FORCETOC__ | __FORCETOC__ | ||
<div class="col-md-12 ibox-content"> | <div class="col-md-12 ibox-content"> | ||
=Current Known Issues= | =Current Known Issues on ZCS 9.0= | ||
<hr> | <hr> | ||
{{KB|{{WIP}}|{{ZCS 9.0}}|}} | {{KB|{{WIP}}|{{ZCS 9.0}}|}} | ||
==Current known issues with ZCS 9.0 patch 28== | |||
'''Summary of the issue:''' Dependancy issue for pcre2 package. | |||
'''Bug number:''' ZBUG-3126 (To be fixed) | |||
'''Description:''' Steps to reproduce: | |||
: Install the latest patch on the ZCS mailbox node (which has no MTA service) | |||
: After package installation, do zmcontrol restart. | |||
: Result: restart will show convertd and spell service failed to start due to missing libpcre2-8.so.0. | |||
'''Workaround:''' Install pcre2-10.23-2.el7.x86_64 manually on the mailbox node. | |||
yum install pcre2-10.23-2.el7.x86_64 | |||
or | |||
apt install pcre2-10.23-2.el7.x86_64 | |||
---- | |||
'''Summary of the issue:''' Error while sending the email. | |||
'''Bug number:''' ZBUG-3129 (To be fixed) | |||
'''Description:''' When sending mail (Or reply mail with attachment or image in signature), it gives an exception. | |||
'''Workaround:''' Disable the attachment scanning: | |||
zmprov ms `zmhostname` zimbraAttachmentsScanEnabled FALSE | |||
zmmailboxdctl restart | |||
---- | |||
'''Summary of the issue:''' Edit single event in series - on android, newly added attendee not getting synced. | |||
'''Bug number:''' ZBUG-3133 (To be fixed) | |||
'''Description:''' On an android device, the newly added attendees not getting synced. Other changes are getting synced. | |||
'''Workaround:''' NA | |||
---- | |||
==Current known issues with ZCS 9.0 patch 25== | ==Current known issues with ZCS 9.0 patch 25== | ||
'''Summary of the issue:''' dns-cache service fails to start after upgrading the server | |||
'''Bug number:''' ZBUG-2929 | |||
'''Description:''' After upgrading the server to ver 9.0 (latest patch), the dns-cache service doesn't start. | |||
'''Workaround:''' Follow the given steps : | |||
1) Comment below line from "/opt/zimbra/conf/unbound.conf.in", | |||
trust-anchor-file: "/opt/zimbra/conf/root.key" | |||
2) Enable the DNS cache service if disabled on server. | |||
3) Restart the Zimbra services on DNS-cache server, | |||
zmcontrol restart | |||
---- | |||
'''Summary of the issue:''' Using the Org Chart in ZWC may cause the webclient to freeze | |||
'''Bug number:''' ZBUG-2853 | |||
'''Description:''' Performing actions such a clicking on a checkbox or minimizing a branch may cause the client to freeze. | |||
'''Workaround:''' NA | |||
---- | |||
====Fixed in the latest packages for patch 25==== | |||
The following bugs have been fixed in the latest packages, but are included here in case someone is still on the old package. | |||
'''Summary of the issue:''' zmconfigd is failing for ldap-only nodes. | '''Summary of the issue:''' zmconfigd is failing for ldap-only nodes. | ||
'''Bug number:''' ZBUG-2837 | '''Bug number:''' <s>ZBUG-2837</s> Fixed in the latest patch packages. | ||
'''Description:''' zmconfigd is failing for ldap-only nodes. | '''Description:''' zmconfigd is failing for ldap-only nodes. | ||
Line 28: | Line 97: | ||
3. Restart zmconfigd | 3. Restart zmconfigd | ||
---- | |||
'''Summary of the issue:''' SMTP authentication failure with 2FA application passcode | '''Summary of the issue:''' SMTP authentication failure with 2FA application passcode | ||
'''Bug number:''' ZBUG-2831 | '''Bug number:''' <s>ZBUG-2831</s> Fixed in the latest patch packages. | ||
'''Description:''' SMTP authentication failure with 2FA application passcode is configured in client like outlook, thunderbird etc. | '''Description:''' SMTP authentication failure with 2FA application passcode is configured in client like outlook, thunderbird etc. | ||
Line 41: | Line 111: | ||
2. Restart mailbox after this | 2. Restart mailbox after this | ||
---- | |||
'''Summary of the issue:''' All Zimlets are disabled from custom COS after redeploying the Zimlets | '''Summary of the issue:''' All Zimlets are disabled from custom COS after redeploying the Zimlets | ||
'''Bug number:''' | '''Bug number:''' <s>ZZBUG-2833</s> Fixed in the latest patch packages. | ||
'''Description:''' When zimlets are redeployed on the server , then zimlets are disabled on the customer COS. | '''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. | '''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. | '''Summary of the issue:''' No INFO logs while redeploying the Zimlets on the server. | ||
'''Bug number:''' ZBUG-2834 | '''Bug number:''' <s>ZBUG-2834</s> Fixed in the latest patch packages. | ||
'''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. | '''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 the backend. | ||
'''Workaround:''' N/A | '''Workaround:''' N/A | ||
---- | |||
'''Summary of the issue:''' /var/log/syslog filling after applying the patch | '''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 | '''Bug number:''' <s>ZBUG-2835</s> Fixed in the latest patch packages. | ||
'''Description:''' /var/log/syslog filling after applying the patch 8.8.15 patch 32. This leads to the disk space filling up. | '''Description:''' /var/log/syslog filling after applying the patch 8.8.15 patch 32. This leads to the disk space filling up. | ||
Line 69: | Line 142: | ||
1. Open /opt/zimbra/conf/log4j.properties.in and update line no 195 and change value to info from debug. | 1. Open /opt/zimbra/conf/log4j.properties.in 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. | |||
---- | |||
==Other issues with ZCS 9.0 patch 25== | |||
* 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 | * 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 | ||
Line 83: | Line 161: | ||
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) | at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) | ||
... 1 more</pre> | ... 1 more</pre> | ||
* 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. | * 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. | * 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. | ||
Line 91: | Line 171: | ||
1. In /opt/zimbra/jetty_base/etc/krb5.ini.in -> [libdefaults] section, set allow_weak_crypto = true | 1. In /opt/zimbra/jetty_base/etc/krb5.ini.in -> [libdefaults] section, set allow_weak_crypto = true | ||
2. Restart mailboxd service: | 2. Restart mailboxd service: | ||
<pre>su - zimbra | <pre>su - zimbra | ||
zmmailboxdctl restart</pre> | zmmailboxdctl restart</pre> |
Revision as of 08:55, 30 November 2022
Current Known Issues on ZCS 9.0
Current known issues with ZCS 9.0 patch 28
Summary of the issue: Dependancy issue for pcre2 package.
Bug number: ZBUG-3126 (To be fixed)
Description: Steps to reproduce:
- Install the latest patch on the ZCS mailbox node (which has no MTA service)
- After package installation, do zmcontrol restart.
- Result: restart will show convertd and spell service failed to start due to missing libpcre2-8.so.0.
Workaround: Install pcre2-10.23-2.el7.x86_64 manually on the mailbox node.
yum install pcre2-10.23-2.el7.x86_64
or
apt install pcre2-10.23-2.el7.x86_64
Summary of the issue: Error while sending the email.
Bug number: ZBUG-3129 (To be fixed)
Description: When sending mail (Or reply mail with attachment or image in signature), it gives an exception.
Workaround: Disable the attachment scanning:
zmprov ms `zmhostname` zimbraAttachmentsScanEnabled FALSE zmmailboxdctl restart
Summary of the issue: Edit single event in series - on android, newly added attendee not getting synced.
Bug number: ZBUG-3133 (To be fixed)
Description: On an android device, the newly added attendees not getting synced. Other changes are getting synced.
Workaround: NA
Current known issues with ZCS 9.0 patch 25
Summary of the issue: dns-cache service fails to start after upgrading the server
Bug number: ZBUG-2929
Description: After upgrading the server to ver 9.0 (latest patch), the dns-cache service doesn't start.
Workaround: Follow the given steps :
1) Comment below line from "/opt/zimbra/conf/unbound.conf.in",
trust-anchor-file: "/opt/zimbra/conf/root.key"
2) Enable the DNS cache service if disabled on server.
3) Restart the Zimbra services on DNS-cache server, zmcontrol restart
Summary of the issue: Using the Org Chart in ZWC may cause the webclient to freeze
Bug number: ZBUG-2853
Description: Performing actions such a clicking on a checkbox or minimizing a branch may cause the client to freeze.
Workaround: NA
Fixed in the latest packages for patch 25
The following bugs have been fixed in the latest packages, but are included here in case someone is still on the old package.
Summary of the issue: zmconfigd is failing for ldap-only nodes.
Bug number: ZBUG-2837 Fixed in the latest patch packages.
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/:
wget https://raw.githubusercontent.com/Zimbra/zm-core-utils/9.0.0.p25/src/libexec/zmconfigd wget https://raw.githubusercontent.com/Zimbra/zm-jython/9.0.0.p25/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
Summary of the issue: SMTP authentication failure with 2FA application passcode
Bug number: ZBUG-2831 Fixed in the latest patch packages.
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/jetty.xml.in 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: ZZBUG-2833 Fixed in the latest patch packages.
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 Fixed in the latest patch packages.
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 the 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 Fixed in the latest patch packages.
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/log4j.properties.in 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.
Other issues with ZCS 9.0 patch 25
- 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. 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/krb5.ini.in -> [libdefaults] section, set allow_weak_crypto = true
2. Restart mailboxd service:
su - zimbra zmmailboxdctl restart