Zimbra 9.0.0 Patch 29 and 8.8.15 Patch 36 Released 8 December - Please Post Your Patching Results Here

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
User avatar
L. Mark Stone
Ambassador
Ambassador
Posts: 2796
Joined: Wed Oct 09, 2013 11:35 am
Location: Portland, Maine, US
ZCS/ZD Version: 10.0.6 Network Edition
Contact:

Zimbra 9.0.0 Patch 29 and 8.8.15 Patch 36 Released 8 December - Please Post Your Patching Results Here

Post by L. Mark Stone »

From the notification:

This patch fixes 2 issues that were introduced with 9.0.0 Patch 28 and 8.8.15 Patch 35.

In the previous patch, ClamAV was upgraded to the latest upstream version and unfortunately broke attachment scanning. This new patch restores the attachment scanning functionality.

Should you have disabled attachment scanning, you can re-enable it by running:

Code: Select all

zmprov ms `zmhostname` zimbraAttachmentsScanEnabled TRUE
zmcontrol restart
 
In the previous patch spell and converted services failed to start on mailstore nodes in a multi node setup. This has been fixed by recompiling Apache with existing PCRE library.

Please refer to the release notes for the patch installation on Red Hat and Ubuntu platforms.

We recommend you upgrade to the latest patch for your version. More information about the recommended patch can be found at:

https://wiki.zimbra.com/wiki/Zimbra_Releases/9.0.0/P29
https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15/P36

Please consider posting your patching results in this thread.

Happy Holidays,
Mark
___________________________________
L. Mark Stone
Mission Critical Email - Zimbra VAR/BSP/Training Partner https://www.missioncriticalemail.com/
AWS Certified Solutions Architect-Associate
Klug
Ambassador
Ambassador
Posts: 2746
Joined: Mon Dec 16, 2013 11:35 am
Location: France - Drôme
ZCS/ZD Version: All of them
Contact:

Re: Zimbra 9.0.0 Patch 28 and 8.8.15 Patch 35 Released 8 December - Please Post Your Patching Results Here

Post by Klug »

Mark, it seems it's only "outgoing" attachment scanning and it's only if you enabled it.
https://wiki.zimbra.com/wiki/Enable_the ... Web_Client

(I changed the subject of the thread to the correct patch numbers)
User avatar
L. Mark Stone
Ambassador
Ambassador
Posts: 2796
Joined: Wed Oct 09, 2013 11:35 am
Location: Portland, Maine, US
ZCS/ZD Version: 10.0.6 Network Edition
Contact:

Re: Zimbra 9.0.0 Patch 29 and 8.8.15 Patch 36 Released 8 December - Please Post Your Patching Results Here

Post by L. Mark Stone »

Thanks for fixing my typos!!
___________________________________
L. Mark Stone
Mission Critical Email - Zimbra VAR/BSP/Training Partner https://www.missioncriticalemail.com/
AWS Certified Solutions Architect-Associate
ghen
Outstanding Member
Outstanding Member
Posts: 258
Joined: Thu May 12, 2016 1:56 pm
Location: Belgium
ZCS/ZD Version: 9.0.0

Re: Zimbra 9.0.0 Patch 29 and 8.8.15 Patch 36 Released 8 December - Please Post Your Patching Results Here

Post by ghen »

Looks like P36 only contains those two fixes and nothing else. So it should be safe for anyone already on P35.
User avatar
gabrieles
Outstanding Member
Outstanding Member
Posts: 233
Joined: Tue Feb 14, 2017 9:40 am

Re: Zimbra 9.0.0 Patch 29 and 8.8.15 Patch 36 Released 8 December - Please Post Your Patching Results Here

Post by gabrieles »

Patched a Centos7 single server from 9.0.0 P26 to P29, it broke something with pax.
It upgraded even the kernel and creating the new images something relative to cpio went wrong.
Installation was done under screen so we haven't more infos.. and reverted immediately to previous snapshot.

We planned another dual step upgrade and will try to upgrade first system packages, then zimbra packages.
User avatar
gabrieles
Outstanding Member
Outstanding Member
Posts: 233
Joined: Tue Feb 14, 2017 9:40 am

Re: Zimbra 9.0.0 Patch 29 and 8.8.15 Patch 36 Released 8 December - Please Post Your Patching Results Here

Post by gabrieles »

Patched yesterday another RHEL7 dual server, frontend+backend 8.8.15 from P33 to P36.
Having been burned from the other one, we did a two step patching for each server: disabled zimbra repo, yum update, reboot, re enabled zimbra repo, patched zimbra, restarted services
No problem emerged in this case.
ghen
Outstanding Member
Outstanding Member
Posts: 258
Joined: Thu May 12, 2016 1:56 pm
Location: Belgium
ZCS/ZD Version: 9.0.0

Re: Zimbra 9.0.0 Patch 29 and 8.8.15 Patch 36 Released 8 December - Please Post Your Patching Results Here

Post by ghen »

gabrieles wrote:Patched a Centos7 single server from 9.0.0 P26 to P29, it broke something with pax.
It upgraded even the kernel and creating the new images something relative to cpio went wrong.
If cpio was removed, you have most likely been compromised via CVE-2022-41352 (amavisd cpio exploit), see similar reports here, here and here.
User avatar
dbayer
Advanced member
Advanced member
Posts: 84
Joined: Thu Oct 09, 2014 9:10 am
Location: Maine
ZCS/ZD Version: Zimbra 10.0.5
Contact:

Re: Zimbra 9.0.0 Patch 29 and 8.8.15 Patch 36 Released 8 December - Please Post Your Patching Results Here

Post by dbayer »

Update on

Ubuntu 18.04
Zimbra 8.8.15p35

When we applied Patch 35, everything seemed to go smoothly.
Now with Patch 36, after a reboot most of the Zimbra Services would not start. For new we just rolled back to the snapshot we took just before updating.
bulletxt
Advanced member
Advanced member
Posts: 81
Joined: Sat Sep 13, 2014 1:08 am

Re: Zimbra 9.0.0 Patch 29 and 8.8.15 Patch 36 Released 8 December - Please Post Your Patching Results Here

Post by bulletxt »

dbayer wrote:Update on

Ubuntu 18.04
Zimbra 8.8.15p35

When we applied Patch 35, everything seemed to go smoothly.
Now with Patch 36, after a reboot most of the Zimbra Services would not start. For new we just rolled back to the snapshot we took just before updating.

That really sounds strange. Considering p36 only fixes a "small" issue I don't see how can that happen. When you have some time I suggest to give a better look at the issue...
User avatar
ccelis5215
Outstanding Member
Outstanding Member
Posts: 632
Joined: Sat Sep 13, 2014 2:04 am
Location: Caracas - Venezuela
ZCS/ZD Version: 8.8.15.GA.3869.UBUNTU18.64 P12

Re: Zimbra 9.0.0 Patch 29 and 8.8.15 Patch 36 Released 8 December - Please Post Your Patching Results Here

Post by ccelis5215 »

Hello,

Just upgrade from P34 to Release 8.8.15.GA.3869.UBUNTU18.64 UBUNTU18_64 FOSS edition, Patch 8.8.15_P36.

Everything seems ok but some errors in zimbra.log

Code: Select all

Dec 20 21:33:45 mailserver zmconfigd[85464]: Rewrite failed: [Errno 2] No such file or directory: '/opt/zimbra/common/conf/master.cf.in' ([Errno 2] No such file or directory: '/opt/zimbra/common/conf/master.cf.in')
Dec 20 21:34:53 mailserver zmconfigd[85464]: Rewrite failed: [Errno 2] No such file or directory: '/opt/zimbra/common/conf/tag_as_originating.re.in' ([Errno 2] No such file or directory: '/opt/zimbra/common/conf/tag_as_originating.re.in')
Dec 20 21:34:53 mailserver zmconfigd[85464]: Rewrite failed: [Errno 2] No such file or directory: '/opt/zimbra/common/conf/tag_as_foreign.re.in' ([Errno 2] No such file or directory: '/opt/zimbra/common/conf/tag_as_foreign.re.in')
After some tests sending and receiving and https://wiki.zimbra.com/wiki/Missing_ma ... rror_-_MTA changing files of course those errors doesn't appear in log.

but /opt/zimbra/common/conf/ looks starnge to says the least

Code: Select all

zimbra@engine:~/common/conf$ ls -slt
total 312
36 -rw-r--r-- 1 root   root   32954 Dec 20 21:57 main.cf
 0 -r--r----- 1 zimbra zimbra     0 Dec 20 21:56 master.cf
 0 -r--r----- 1 zimbra zimbra     0 Dec 20 21:56 tag_as_foreign.re
 0 -r--r----- 1 zimbra zimbra     0 Dec 20 21:56 tag_as_originating.re
 0 -rw-r----- 1 zimbra zimbra     0 Dec 20 21:42 tag_as_foreign.re.in
 0 -rw-r----- 1 zimbra zimbra     0 Dec 20 21:42 tag_as_originating.re.in
 0 -rw-r----- 1 zimbra zimbra     0 Dec 20 21:41 master.cf.in
28 -rw-r--r-- 1 root   zimbra 26493 Jun 30  2021 LICENSE
 4 -rw-r--r-- 1 root   zimbra  1629 Jun 30  2021 TLS_LICENSE
24 -rw-r--r-- 1 root   zimbra 21111 Jun 30  2021 access
12 -rw-r--r-- 1 root   zimbra 10519 Jun 30  2021 aliases
 4 -rw-r--r-- 1 root   zimbra  3547 Jun 30  2021 bounce.cf.default
16 -rw-r--r-- 1 root   zimbra 13194 Jun 30  2021 canonical
12 -rw-r--r-- 1 root   zimbra 10221 Jun 30  2021 generic
24 -rw-r--r-- 1 root   zimbra 23802 Jun 30  2021 header_checks
40 -rw-r--r-- 1 root   zimbra 38573 Jun 30  2021 main.cf.default
28 -rw-r--r-- 1 root   zimbra 28078 Jun 30  2021 main.cf.proto
 8 -rw-r--r-- 1 root   zimbra  4217 Jun 30  2021 makedefs.out
 8 -rw-r--r-- 1 root   zimbra  6629 Jun 30  2021 master.cf.proto
20 -rw-r--r-- 1 root   zimbra 20463 Jun 30  2021 postfix-files
 8 -rw-r--r-- 1 root   zimbra  6929 Jun 30  2021 relocated
16 -rw-r--r-- 1 root   zimbra 13442 Jun 30  2021 transport
16 -rw-r--r-- 1 root   zimbra 13963 Jun 30  2021 virtual
 4 -rw-rw-r-- 1 root   root    2241 Sep 17  2019 snmp.conf
 4 drwxr-xr-x 2 root   zimbra  4096 May  1  2015 postfix-files.d
What do you think? Your comments will be welcomed.

ccelis
Post Reply