8.8.15 Patch 32 GA Release

[bulletxt]

Hi,
anyone upgraded to this patch? Please share experience

Thanks

[L. Mark Stone]

I have not yet applied the patch, but I did open a Support Case to get clarity around the upgrade order and specifics as to the new procedure for updating mailstores.

Essentially, I was told so far:

1. In a multi-server environment, the normal upgrade order of LDAP servers > MTA servers > Proxy servers > Mailstores still applies.

2. Identify which NG component packages you have already on your mailstores. Use like dpkg -l <package name> to look for any of the following:

Code: Select all

dpkg -l | grep zimbra-network-modules-ng
dpkg -l | grep zimbra-connect
dpkg -l | grep zimbra-zimlet-auth
dpkg -l | grep zimbra-docs
dpkg -l | grep zimbra-drive-ng

Make a list of which of the above packages are installed on your mailstores (needed for the next step).

3. When you get to the mailstores, you should run in order:

Code: Select all

apt-get update
apt-get install zimbra-common-core-jar zimbra-common-core-libs zimbra-mbox-store-libs
apt-get install zimbra-patch zimbra-apache-components zimbra-spell-components
apt-get install zimbra-network-modules-ng (only if this package is already installed)
apt-get install zimbra-connect (only if this package is already installed)
apt-get install zimbra-zimlet-auth (only if this package is already installed)
apt-get install zimbra-docs (only if this package is already installed)
apt-get install zimbra-drive-ng (only if this package is already installed)
su - zimbra
zmcontrol restart


Assuming everything looks good and Zimbra restarts OK, you can then update the operating system, to get security, kernel and other updates (as root of course...):

Code: Select all

apt-get dist-upgrade

The server should then be rebooted. I prefer to do this by stopping Zimbra manually, as the zimbra user:

Code: Select all

zmcontrol stop && exit
reboot now

Two of my servers are combo LDAP MMR/MTA/Proxy servers, and I have a clarifying question about their upgrade process in to Support. I'll update this post once I hear back. 15 June Update: Support has responded for my LDAP MMR/MTA/Proxy servers:

Code: Select all

apt-get update
apt-get install zimbra-ldap-components zimbra-proxy-patch  zimbra-proxy-components zimbra-snmp-components  zimbra-mta-components zimbra-mta-patch
su - zimbra
zmcontrol restart
exit
apt-get dist-upgrade
su - zimbra
zmcontrol stop && exit
reboot now

Hope that helps.

All the best,
Mark

[JonathanDelgado]

Subsequent to upgrading I started getting errors in my zimbra.log like:

Code: Select all

unbound: [3701:0] info: generate keytag query _ta-4f66. NULL IN
unbound: [3701:0] info: failed to prime trust anchor -- DNSKEY rrset is not secure . DNSKEY IN


and DNS requests were failing. I've added the Google DNS server 8.8.8.8 and reloaded the DNS caching ( following https://wiki.zimbra.com/wiki/DNS_cachin ... _(dnscache) ) and that seems to have fixed things for the moment, but there is clearly something unhappy about the changes made in this patch, perhaps due to

ZBUG-2723 dnscache service does not support DNSSEC validation

in the release notes. Purely speculation though at this point.

[Seb]

I did the update this morning.

After restarting all the services, Suite Plus stopped working.

A lot of administration errors of UNKOWN_DOCUMENT.
CLI of zxsuite keeps saying "Unable to communicate with server".

Have not found a solution yet.

[L. Mark Stone]

I did the update this morning.

After restarting all the services, Suite Plus stopped working.

A lot of administration errors of UNKOWN_DOCUMENT.
CLI of zxsuite keeps saying "Unable to communicate with server".

Have not found a solution yet.

With a ZSP Subscription you are entitled to open a Support Case with Zimbra. I would open it as a Sev-1 as your system is down.

Hope that helps,
Mark

[Seb]

Hi L . Mark Stone,

This is my next move.
Fortunately, most of the system (sending/receiving) is ok.

I mainly gave this information if others have the same problem.

[dcasanov]

Hi,

after upgrade in a multi-server environment on RHEL8, Zimbra Network Edition, on ldap, mta and proxy servers, the zmconfigd failed:

Code: Select all

[zimbra@zldap31 ~]$ zmconfigdctl restart
Stopping zmconfigd...zmconfigd is not running.
Starting zmconfigd...failed.

I don't see any interesting logs

When I try to start manually, I get:

Code: Select all

[zimbra@zldap31 ~]$ libexec/zmconfigd
Jun 15, 2022 9:33:42 PM org.python.google.common.base.internal.Finalizer getInheritableThreadLocalsField
INFO: Couldn't access Thread.inheritableThreadLocals. Reference finalizer threads will inherit thread local values.
Traceback (most recent call last):
  File "libexec/zmconfigd", line 32, in <module>
    from org.apache.log4j import PropertyConfigurator
ImportError: No module named apache

On mailstore servers, zmconfigd is ok.

[ppraly]

Hi,

You have to check that zmconfigd is not already running ?

[dcasanov]

Hi,

yes I checked, no pid in /opt/zimbra/log

I don't have IPv6 enabled and I've nc installed.

[M_vdM]

Code: Select all

Jun 16, 2022 10:23:17 AM org.python.google.common.base.internal.Finalizer getInheritableThreadLocalsField
INFO: Couldn't access Thread.inheritableThreadLocals. Reference finalizer threads will inherit thread local values.
Traceback (most recent call last):
  File "libexec/zmconfigd", line 32, in <module>
    from org.apache.log4j import PropertyConfigurator
ImportError: No module named apache


Same problem over here with zmconfigd after updating the ldap server(s).