Post-June 17 Patch 25/32 Success Stories Roll Call

[L. Mark Stone]

If you've successfully installed Patch 25/32 after the fixes were slipstreamed in and the repos were reopened yesterday, it would be helpful if you could post here please your results.

In your post, if you wouldn't mind including please:

-- Was this a fresh install or did you apply the patch to an existing system? (Please indicate single or multi-server)

-- Did you follow the instructions in the "Installing zimbra packages with system package upgrades" section of the Release Notes which direct you, on mailstore servers only, to install the zimbra-common-core-jar, zimbra-common-core-libs, and zimbra-mbox-store-libs packages first before installing any other updates?

-- Did you need to (or choose to) apply any pre-patch or post-patch changes, like for single-sign-on or to enable LC zimbra_external_email_warning_enabled and zimbra_external_email_warning_message, and; how did that go?

-- The output from "zmcontrol -v"

-- Anything else you feel would be helpful to others.

From talking to customers my sense is many of us running more mission-critical systems are, let's say, "at a heightened state of awareness" at this moment, and so we'd all be grateful to those who have taken the plunge with the now re-released patches.

Thanks!

All the best,
Mark

[axslingr]

Fresh 8.8.15FOSS install on Centos7 worked as expected so this is good! Did not install Drive or Chat. No other changes made. I have another Centos7 server running 8.8.15NE_P30 and another Ubuntu 18 running 8.8.15FOSS_P30 w/Zextras that I'm working up the nerve to upgrade.

Code: Select all

[zimbra@mail ~]$ zmcontrol -v    
Release 8.8.15_GA_3869.RHEL7_64_20190917004220 RHEL7_64 FOSS edition, Patch 8.8.15_P32.

-- Did you follow the instructions in the "Installing zimbra packages with system package upgrades" section of the Release Notes which direct you, on mailstore servers only, to install the zimbra-common-core-jar, zimbra-common-core-libs, and zimbra-mbox-store-libs packages first before installing any other updates?

Is there a way to skip the patch during a fresh install? I'd love to test this out without following instructions. Seems a bit dangerous to require this extra step.

Lance

[JDunphy]

Single server on RHEL 8.6. Restored last nights backup of production server to new vm and applied update against that instance. 8.8.15.P31.1 to 8.8.15P32

Code: Select all

% zmcontrol -v
Release 8.8.15_GA_3953.RHEL8_64_20200629025823 RHEL8_64 NETWORK edition, Patch 8.8.15_P32.

Uneventful and everything up and running. Not tested much at this point but no fatal or errors in the logs either. Tested my user account and Admin interfaces using 2FA - no issues. Admin interface reports Version 8.8.15_GA_4308.NETWORK Jun 17, 2022 and everything looks normal. NG Backups seems happy and working. Went looking for extra debugging information in logs, and could not find anything but am watching the logs given a few reports of disk space from the forums.

I don't trust it at this point but that is normal after any change to software. I'll let it run this way for a few days and do some additional testing and then decide when we schedule it into production. Note: the zimlet update process was long enough that I went looking to see if my update had stalled or got stuck. Serious paranoia from me today.

Oh, don't know if this is a RHEL thing but I tried the 3 jar files first from the release notes and yum reported they were installed and then aborted. Forged ahead and did a yum update followed by a zmcontrol restart with no issues.

Code: Select all

# yum install zimbra-common-core-jar zimbra-common-core-libs zimbra-mbox-store-libs
Last metadata expiration check: 9:39:39 ago on Sat 18 Jun 2022 02:51:28 AM PDT.
Package zimbra-common-core-jar-8.8.15.1651868636-1.r8.x86_64 is already installed.
Package zimbra-common-core-libs-8.8.15.1650522012-1.r8.x86_64 is already installed.
Package zimbra-mbox-store-libs-8.8.15.1647230035-1.r8.x86_64 is already installed.
Dependencies resolved.
========================================================================================================================
 Package                           Architecture     Version                             Repository                 Size
========================================================================================================================
Upgrading:
 zimbra-common-core-jar            x86_64           8.8.15.1655458176-1.r8              zimbra-8815-oss            13 M
 zimbra-common-core-libs           x86_64           8.8.15.1654854265-1.r8              zimbra-8815-oss            65 M
 zimbra-mbox-store-libs            x86_64           8.8.15.1654854265-1.r8              zimbra-8815-oss            37 M

Transaction Summary
========================================================================================================================
Upgrade  3 Packages

Total download size: 116 M
Is this ok [y/N]: Operation aborted.

Here is what was updated.

Code: Select all

# yum update
Last metadata expiration check: 9:40:57 ago on Sat 18 Jun 2022 02:51:28 AM PDT.
Dependencies resolved.
========================================================================================================================
 Package                              Architecture  Version                            Repository                  Size
========================================================================================================================
Upgrading:
 zimbra-clamav                        x86_64        0.103.3-1zimbra8.8b3.el8           zimbra-8815-oss            283 k
 zimbra-clamav-libs                   x86_64        0.103.3-1zimbra8.8b3.el8           zimbra-8815-oss            3.4 M
 zimbra-common-core-jar               x86_64        8.8.15.1655458176-1.r8             zimbra-8815-oss             13 M
 zimbra-common-core-libs              x86_64        8.8.15.1654854265-1.r8             zimbra-8815-oss             65 M
 zimbra-common-mbox-conf-attrs        x86_64        8.8.15.1652767386-1.r8             zimbra-8815-oss             94 k
 zimbra-common-mbox-conf-msgs         x86_64        8.8.15.1652703447-1.r8             zimbra-8815-oss            644 k
 zimbra-core-components               x86_64        2.0.16-1zimbra8.8b1.el8            zimbra-8815-oss            9.5 k
 zimbra-jetty-distribution            x86_64        9.4.46.v20220331-2.r8              zimbra-8815-oss             17 M
 zimbra-ldap-components               x86_64        1.0.16-1zimbra8.8b1.el8            zimbra-8815-oss            9.2 k
 zimbra-license-tools                 x86_64        8.8.15.1651485155-1.r8             zimbra-8815-network         61 k
 zimbra-mbox-admin-console-war        x86_64        8.8.15.1653031987-1.r8             zimbra-8815-oss             12 M
 zimbra-mbox-ews-service              x86_64        8.8.15.1654977069-1.r8             zimbra-8815-network        1.3 M
 zimbra-mbox-store-libs               x86_64        8.8.15.1654854265-1.r8             zimbra-8815-oss             37 M
 zimbra-mbox-war                      x86_64        8.8.15.1655458176-1.r8             zimbra-8815-oss             23 M
 zimbra-mbox-webclient-war            x86_64        8.8.15.1654769776-1.r8             zimbra-8815-oss             25 M
 zimbra-mta-components                x86_64        1.0.15-1zimbra8.8b1.el8            zimbra-8815-oss            9.4 k
 zimbra-mta-patch                     x86_64        8.8.15.1655471268.p32-1.r8         zimbra-8815-oss             47 k
 zimbra-network-modules-ng            x86_64        6.0.34.1652960218-1.r8             zimbra-8815-network         95 M
 zimbra-openjdk                       x86_64        17.0.2-1zimbra8.8b1.el8            zimbra-8815-oss            160 M
 zimbra-openssl                       x86_64        1.1.1n-1zimbra8.7b4.el8            zimbra-8815-oss            2.2 M
 zimbra-openssl-libs                  x86_64        1.1.1n-1zimbra8.7b4.el8            zimbra-8815-oss            5.6 M
 zimbra-patch                         x86_64        8.8.15.1655471268.p32-2.r8         zimbra-8815-network        103 M
 zimbra-perl-mail-spamassassin        x86_64        3.4.6-1zimbra8.8b4.el8             zimbra-8815-oss            798 k
 zimbra-proxy-patch                   x86_64        8.8.15.1655471268.p32-1.r8         zimbra-8815-oss             50 k
 zimbra-spamassassin-rules            x86_64        1.0.0-1zimbra8.8b6.el8             zimbra-8815-oss            277 k

Transaction Summary
========================================================================================================================
Upgrade  25 Packages

Total download size: 565 M
Is this ok [y/N]: y
...
...

Edit/updated: Found an info message I have not seen before. It is only once so far.

Code: Select all

tail -f zmmailboxd.out
[1414.888s][info][gc] GC(20) Concurrent Mark Cycle 391.381ms
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
------------------- TRACE (sent) -----------------------
LOCK, arg=license_email_lock, trylock=true, timeout=5000
--------------------------------------------------------
------------------- TRACE (sent) -----------------------
UNLOCK, arg=license_email_lock, trylock=false, timeout=0
--------------------------------------------------------

HTH,

Jim

[gmills]

8.8.15 FOSS on Centos 7 multi server (ldap server, MTA/store/proxy server, proxy server)

Release 8.8.15_GA_3869.RHEL7_64_20190917004220 RHEL7_64 FOSS edition, Patch 8.8.15_P32.

June 14
I installed the original P32 patch on 14 June successfully (I thought)
I followed the RedHat instructions in the Release notes, luckily I saw " Important! Please note that the install process has changed" [this really should have been displayed prominently I remember thinking at that time]. I updated all 3 servers (ldap, store, proxy) one by one as per the notes. The upgrade worked OK.

I was very pleased because now I could log into the proxy server reliably whereas been having issues for a long time with this (would not log in or html frames were missing). SameSite cookie issue I suspect.

June 18
New set of patches so this time I ran a simple 'yum update' figuring these would replace the ones in place already... oops!
The LDAP Server would not load zmconfigd - Checked Zimbra forums and found out that P32 was flawed and realised I had struck other issues.

Issues:
- LDAP issue was resolved from messages in this forum
- Zextras suite had stopped working (no backups). Downloaded latest zextra_suite release and reinstalled - working again
- Store server is logging copious data in /var/log/messages (seperate thread in this forum) from mailboxd INFO & DEBUG, looks like zmstat related.
The 2nd patch removed the DEBUG entries. The Zimbra workaround does not apply to Centos setup (that I can work out)

"apply any pre-patch or post-patch changes" - None of these changes were made
FWIW had already reconfigured ZCS for TLS1.3 and removed TLS1.0

Regards
Geoffrey Mills

[barrydegraaff]

Hello All,

Just to let you know I did update the sales demo server on Saturday, the server is used to offer the online demo via zimbra.com.

It is on CentOS 7 and updated from patch 24.1 to 25 without issues.

[Andreas.M]

Hello,

did the patch32 upgrade after Notice "Clear to proceed", update finished successfully, but zxsuite (Zimbra Suite Plus Bundle) is not working anymore. Reinstall of ZSP also didn't help.

Release 8.8.15_GA_3829.RHEL7_64_20190718141144 RHEL7_64 FOSS edition, Patch 8.8.15_P32.
Single Server centOS 7.9
Install procedure according release notes
no SSO etc

Status:
basic functionality ok (imap/pop/smtp/webgui), but
zxsuite error - unable to connect to server
therefore ActiveSync (aka mobilesync) Protocol not available
admin WebGui - zxsuite module symbols are shown, but without functionality
cannot edit any account in WebGui (Error: JavaScript Error encountered in method ZAcontroller.prototype.changeActionsState)

Is it a Success Story? not sure ...

br Andreas

UPDATE:
just got the info from support that new version zsp 1.3.5 is available for download, the installation fixed all problems with zxsuite.
So now it's a Success Story, thanks to support.

[Martinwiertz]

Before P25 I had a running system on Zimbra Zextras P24. P25 came from zimbra repos and stopped the system.

• I have restored the system to backup P23 and imported the mail (Ubuntu18.04.6 patched)
  Upgraded to Zextras version 2022-04-02 + P24 - all went fine, running system and several reboots and new mail coming in
  Installed P25 via Zimbra repos and system broke again

[L. Mark Stone]

Hello,

did the patch32 upgrade after Notice "Clear to proceed", update finished successfully, but zxsuite (Zimbra Suite Plus Bundle) is not working anymore. Reinstall of ZSP also didn't help.

Release 8.8.15_GA_3829.RHEL7_64_20190718141144 RHEL7_64 FOSS edition, Patch 8.8.15_P32.
Single Server centOS 7.9
Install procedure according release notes
no SSO etc

Status:
basic functionality ok (imap/pop/smtp/webgui), but
zxsuite error - unable to connect to server
therefore ActiveSync (aka mobilesync) Protocol not available
admin WebGui - zxsuite module symbols are shown, but without functionality
cannot edit any account in WebGui (Error: JavaScript Error encountered in method ZAcontroller.prototype.changeActionsState)

Is it a Success Story? not sure ...

br Andreas

Hi Andreas,

Thanks for posting. ZSP is not at this writing supported for this patch. A note was added to the Release Notes about this, just below the "Clear to proceed" message block.

You are entitled to open a Support Case with Zimbra to get help making your system functional again. Suggest you open it as a Sev-1, as your system is down.

[Andreas.M]

Hello Mark,

thank you for your answer. I will open the support case tomorrow (my) morning.

ZSP is not at this writing supported for this patch. A note was added to the Release Notes about this, just below the "Clear to proceed" message block.

That's the point. I read the initial note in the Release Notes and therefore didn't run the update, but when i saw the "Clear to proceed" note, i thought it is also valid for the ZSP ... Somehow misleading, but maybe just for me ...

br Andreas

[darkfader]

Hello All,

Just to let you know I did update the sales demo server on Saturday, the server is used to offer the online demo via zimbra.com.

It is on CentOS 7 and updated from patch 24.1 to 25 without issues.

its kinda telling that this demo system is running on a distro that is on the last 20% of its lifespan.
please, can you try to expose yourself to at least the same issues / business risk? when it still hurts you and can be fixed with fast turnaround - and does not yet hit the existing customer base & community?

Florian