<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Le 16/04/2018 à 15:38, Barry de Graaff
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:1676512758.1539.1523885938325.JavaMail.zimbra@localhost">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div>Those are crystal ball questions to me.</div>
<div><br>
</div>
<div>I think it may be wise to disable all zimbra repos, to avoid
issues if you are using yum-cron or unattended-upgrades.</div>
<div><br>
</div>
<div>Or in case someone installs OS upgrades, unaware of the
zimbra situation. For most sysadmins, the expected behavior may
not be what zimbra does.</div>
</blockquote>
<br>
I see we share the same habits. <span class="moz-smiley-s5"><span>:-D</span></span><br>
<br>
Frédéric.<br>
<blockquote type="cite"
cite="mid:1676512758.1539.1523885938325.JavaMail.zimbra@localhost">
<div><br>
On 16 Apr 2018, at 15:34, Frédéric Nass <<a
href="mailto:frederic.nass@univ-lorraine.fr"
moz-do-not-send="true">frederic.nass@univ-lorraine.fr</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Le 16/04/2018 à 15:26, Barry de
Graaff a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:93810951.1429.1523885214181.JavaMail.zimbra@localhost">
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<div>The upgrade to 8.8.8 is done with a tgz.</div>
<div><br>
</div>
<div>The only new thing is the deployment of the patch via a
repo.</div>
</blockquote>
<br>
Thank you Barry for the explanation. Do you have any idea if
any of those are right :<br>
<br>
- Minor updates won't ever come from repos. Only patches will
from repo "zimbra-888-patch". So downloading tarballs will
always be required for minor updates.<br>
- Minor updates will come from repo "zimbra" and patches from
repo "zimbra-888-patch". So downloading tarballs will only be
required on initial ZCS installation.<br>
<br>
By the way, there's another "zimbra-v1" with no packages on
it. This also is a mystery to me.<br>
<br>
Frédéric.<br>
<blockquote type="cite"
cite="mid:93810951.1429.1523885214181.JavaMail.zimbra@localhost">
<div><br>
</div>
<div>I wonder why the decision has been made to have
separate repos though.</div>
<div><br>
</div>
<div>In addition, the patch requires some parts of Zimbra
restarted.</div>
<div><br>
</div>
<div>So all in all, still some manual work, why not use one
repo per mayor release and then allow yum-cron to do the
rest?</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
On 16 Apr 2018, at 15:17, Frédéric Nass <<a
href="mailto:frederic.nass@univ-lorraine.fr"
moz-do-not-send="true">frederic.nass@univ-lorraine.fr</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p>Hi Mark,</p>
<p><br>
</p>
<p>Same here. I would expect the zimbra-patch package to
be updated along with other packages so that it gets
applied / reapplied when updates come out. I don't
know.<br>
</p>
<p><br>
</p>
<p>I'm still in the process of figuring out how minor
updates should be applied, from the repos or by
downloading the tarball and running ./install.sh as
before.<br>
</p>
<p>I thought that minor updates would not come from the
repos but apparently not. I'm running ZCS 8.8.7 on a
test VM and a yum update shows absolutely _no_ ZCS
8.8.8 updates. :-/</p>
<p><br>
</p>
<p>This is so obscure.</p>
<p><br>
</p>
<p>Regards,</p>
<p><br>
</p>
<p>Frédéric.</p>
<br>
<div class="moz-cite-prefix">Le 14/04/2018 à 13:15, L
Mark Stone a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:BL0PR16MB2225E7FE58C65A2542F21DDCB5B20@BL0PR16MB2225.namprd16.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;"
dir="ltr">
<p style="margin-top:0;margin-bottom:0">OK, I am so
confused...</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">On one
Zimbra system I have automatic updates configured,
so the system upgraded, from the repos, various
zimbra packages including <span
style="font-variant-ligatures:
no-common-ligatures; font-family: Menlo;
font-size: 14px;">zimbra-chat
zimbra-mbox-webclient-war
zimbra-network-modules-ng</span></p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">After that
update completed I then installed the patch. </p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">On another
Zimbra system, I ran apt-get update; apt-get
install zimbra-patch as per the release notes.
The patch installed fine, but if I run apt-get
update AFTER the patch was installed, those three
zimbra packages are still available for updating.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">So I have
two questions.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">First, as
the updated Zimbra packages were released on the
same day/time as the patch, I'm assuming they are
connected somehow. If so, the what's the correct
installation order? Install the packages updates
first, then the patch, or vica versa?</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Second
question is thinking ahead a few weeks. Zimbra
updates their repos, so an apt-get update; apt-get
upgrade updates some Zimbra packages. Do I now
need to reinstall the patch? </p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Thanks,</p>
<p style="margin-top:0;margin-bottom:0">Mark</p>
<div id="Signature">
<div id="divtagdefaultwrapper" dir="ltr"
style="font-size: 12pt; color: rgb(0, 0, 0);
background-color: rgb(255, 255, 255);
font-family: Calibri, Arial, Helvetica,
sans-serif, Helvetica, EmojiFont, "Apple
Color Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol",
"Android Emoji", EmojiSymbols;">
<p><strong>_________________________________________________</strong></p>
<p><strong>Another Message From... L. Mark
Stone</strong></p>
<p><br>
</p>
<p>See my <a
href="https://www.linkedin.com/in/lmarkstone"
id="LPNoLP" moz-do-not-send="true">LinkedIn
Profile</a></p>
<p><br>
</p>
</div>
</div>
</div>
<hr style="display:inline-block;width:98%"
tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt" color="#000000"
face="Calibri, sans-serif"><b>From:</b> Users <a
class="moz-txt-link-rfc2396E"
href="mailto:users-bounces@lists.zetalliance.org"
moz-do-not-send="true"><users-bounces@lists.zetalliance.org></a>
on behalf of Barry de Graaff <a
class="moz-txt-link-rfc2396E"
href="mailto:info@barrydegraaff.tk"
moz-do-not-send="true"><info@barrydegraaff.tk></a><br>
<b>Sent:</b> Saturday, April 14, 2018 3:42:54 AM<br>
<b>To:</b> Tony Publiski<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated"
href="mailto:users@lists.zetalliance.org"
moz-do-not-send="true">users@lists.zetalliance.org</a>;
Phil Pearl<br>
<b>Subject:</b> Re: [Users] Zimbra 8.8.8 Patch 1
release - Seems to break FOSS only servers</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span
style="font-size:11pt;">
<div class="PlainText">Yeah that works well, and
it is also in the release notes... so my bad!<br>
<br>
Kind regards, <br>
<br>
Barry de Graaff<br>
Zeta Alliance <br>
Co-founder & Developer<br>
<a href="http://zetalliance.org"
moz-do-not-send="true">zetalliance.org</a> |
<a href="http://github.com/Zimbra-Community"
moz-do-not-send="true">github.com/Zimbra-Community</a><br>
<br>
+31 617 220 227 | skype: barrydegraaff.tk<br>
Fingerprint:
97f4694a1d9aedad012533db725ddd156d36a2d0<br>
<br>
----- Original Message -----<br>
From: "Tony Publiski" <a
class="moz-txt-link-rfc2396E"
href="mailto:tonster@tonster.com"
moz-do-not-send="true"><tonster@tonster.com></a><br>
To: "Barry en Katie de Graaff" <a
class="moz-txt-link-rfc2396E"
href="mailto:info@barrydegraaff.tk"
moz-do-not-send="true"><info@barrydegraaff.tk></a>,
"Malte S. Stretz" <a
class="moz-txt-link-rfc2396E"
href="mailto:mss@msquadrat.de"
moz-do-not-send="true"><mss@msquadrat.de></a><br>
Cc: "Phil Pearl" <a
class="moz-txt-link-rfc2396E"
href="mailto:ppearl@zimbra.com"
moz-do-not-send="true"><ppearl@zimbra.com></a>,
<a class="moz-txt-link-abbreviated"
href="mailto:users@lists.zetalliance.org"
moz-do-not-send="true">users@lists.zetalliance.org</a><br>
Sent: Friday, April 13, 2018 7:36:54 PM<br>
Subject: Re[3]: [Users] Zimbra 8.8.8 Patch 1
release - Seems to break FOSS only servers<br>
<br>
Hello again!<br>
<br>
Here's the response I got from engineering
toda:<br>
<br>
I looked at installation steps. It looks like,
they are using yum update <br>
-y to install patch packages.<br>
<br>
Instead, they should use below commands to
install the patch:<br>
yum --disablerepo=*
--enablerepo=zimbra-888-patch clean metadata<br>
yum check-update --disablerepo=*
--enablerepo=zimbra-888-patch --noplugins<br>
yum install zimbra-patch<br>
<br>
Let me know if this helps!<br>
<br>
Tony<br>
<br>
------ Original Message ------<br>
From: "Tony Publiski" <a
class="moz-txt-link-rfc2396E"
href="mailto:tonster@tonster.com"
moz-do-not-send="true"><tonster@tonster.com></a><br>
To: "Barry de Graaff" <a
class="moz-txt-link-rfc2396E"
href="mailto:info@barrydegraaff.tk"
moz-do-not-send="true"><info@barrydegraaff.tk></a>;
"Malte S. Stretz" <br>
<a class="moz-txt-link-rfc2396E"
href="mailto:mss@msquadrat.de"
moz-do-not-send="true"><mss@msquadrat.de></a><br>
Cc: "Phil Pearl" <a
class="moz-txt-link-rfc2396E"
href="mailto:ppearl@zimbra.com"
moz-do-not-send="true"><ppearl@zimbra.com></a>;
<a class="moz-txt-link-abbreviated"
href="mailto:users@lists.zetalliance.org"
moz-do-not-send="true">users@lists.zetalliance.org</a><br>
Sent: 4/13/2018 9:53:01 AM<br>
Subject: Re[2]: [Users] Zimbra 8.8.8 Patch 1
release - Seems to break <br>
FOSS only servers<br>
<br>
>Hi Barry,<br>
><br>
>Nice find. I'll take a look and see what
engineering has to say.<br>
><br>
>Tony<br>
><br>
>------ Original Message ------<br>
>From: "Barry de Graaff" <a
class="moz-txt-link-rfc2396E"
href="mailto:info@barrydegraaff.tk"
moz-do-not-send="true"><info@barrydegraaff.tk></a><br>
>To: "Malte S. Stretz" <a
class="moz-txt-link-rfc2396E"
href="mailto:mss@msquadrat.de"
moz-do-not-send="true"><mss@msquadrat.de></a><br>
>Cc: "Tony Publiski" <a
class="moz-txt-link-rfc2396E"
href="mailto:tonster@tonster.com"
moz-do-not-send="true"><tonster@tonster.com></a>;
"Phil Pearl" <br>
><a class="moz-txt-link-rfc2396E"
href="mailto:ppearl@zimbra.com"
moz-do-not-send="true"><ppearl@zimbra.com></a>;
<a class="moz-txt-link-abbreviated"
href="mailto:users@lists.zetalliance.org"
moz-do-not-send="true">users@lists.zetalliance.org</a><br>
>Sent: 4/13/2018 4:41:18 AM<br>
>Subject: Re: [Users] Zimbra 8.8.8 Patch 1
release - Seems to break FOSS <br>
>only servers<br>
><br>
>>No this was always FOSS only, not
Zextras no Talk none of that.<br>
>><br>
>>Kind regards,<br>
>><br>
>>Barry de Graaff<br>
>>Zeta Alliance<br>
>>Co-founder & Developer<br>
>><a href="http://zetalliance.org"
moz-do-not-send="true">zetalliance.org</a> |
<a href="http://github.com/Zimbra-Community"
moz-do-not-send="true">github.com/Zimbra-Community</a><br>
>><br>
>>+31 617 220 227 | skype:
barrydegraaff.tk<br>
>>Fingerprint:
97f4694a1d9aedad012533db725ddd156d36a2d0<br>
>><br>
>>----- Original Message -----<br>
>>From: "Malte S. Stretz" <a
class="moz-txt-link-rfc2396E"
href="mailto:mss@msquadrat.de"
moz-do-not-send="true"><mss@msquadrat.de></a><br>
>>To: "Barry en Katie de Graaff" <a
class="moz-txt-link-rfc2396E"
href="mailto:info@barrydegraaff.tk"
moz-do-not-send="true"><info@barrydegraaff.tk></a><br>
>>Cc: "Tony Publiski" <a
class="moz-txt-link-rfc2396E"
href="mailto:tonster@tonster.com"
moz-do-not-send="true"><tonster@tonster.com></a>,
"Phil Pearl" <br>
>><a class="moz-txt-link-rfc2396E"
href="mailto:ppearl@zimbra.com"
moz-do-not-send="true"><ppearl@zimbra.com></a>,
<a class="moz-txt-link-abbreviated"
href="mailto:users@lists.zetalliance.org"
moz-do-not-send="true">users@lists.zetalliance.org</a><br>
>>Sent: Friday, April 13, 2018 10:35:12
AM<br>
>>Subject: Re: [Users] Zimbra 8.8.8
Patch 1 release - Seems to break <br>
>>FOSS only servers<br>
>><br>
>>Hi Barry,<br>
>><br>
>><br>
>>I always have trouble reading the
dependency output of yum but to me <br>
>>it<br>
>>looks like zimbra-network-modules-ng
is pulled in by zimbra-talk. <br>
>>Which<br>
>>isn't supported for FOSS and shouldn't
appear in the dependency tree <br>
>>at<br>
>>all. Especially both zimbra-chat and
zimbra-talk shouldn't appear at <br>
>>the<br>
>>same time.<br>
>><br>
>><br>
>>Did you by any chance downgrade this
system from NE to FOSS at<br>
>>somepoint? Since this sounds a bit
like the issue I had with such a<br>
>>downgrade on Ubuntu and for which I
filed<br>
>><a
href="https://bugzilla.zimbra.com/show_bug.cgi?id=108911"
moz-do-not-send="true">https://bugzilla.zimbra.com/show_bug.cgi?id=108911</a><br>
>><br>
>><br>
>>Cheers,<br>
>><br>
>>Malte<br>
>><br>
>><br>
>><br>
>>On 13.04.2018 09:13, Barry de Graaff
wrote:<br>
>>>Hello Tony and Phil,<br>
>>><br>
>>>It seems the patch 8.8.8 p1 is
distributed via the repos.<br>
>>><br>
>>>It does NOT seem to work if one
runs a FOSS only server (aka without<br>
>>>Zextras).<br>
>>><br>
>>>I am addressing Phil as there is a
CVE 5.8 Major security fix in the<br>
>>>patch.<br>
>>><br>
>>>[root@zimbra1 ~]# yum update -y<br>
>>>Loaded plugins: fastestmirror,
langpacks<br>
>>>Loading mirror speeds from cached
hostfile<br>
>>>* base: <a
href="http://centos.mirror.triple-it.nl"
moz-do-not-send="true">centos.mirror.triple-it.nl</a><br>
>>>* epel: <a
href="http://mirror.1000mbps.com"
moz-do-not-send="true">mirror.1000mbps.com</a><br>
>>>* extras: <a
href="http://mirror.denit.net"
moz-do-not-send="true">mirror.denit.net</a><br>
>>>* updates: <a
href="http://mirror.prolocation.net"
moz-do-not-send="true">mirror.prolocation.net</a><br>
>>>Resolving Dependencies<br>
>>>--> Running transaction check<br>
>>>---> Package zimbra-chat.x86_64
0:1.0.13.1521626727-2.r7 will be <br>
>>>obsoleted<br>
>>>---> Package
zimbra-common-core-jar.x86_64
0:1.0.0.1521707697-1.r7<br>
>>>will be updated<br>
>>>---> Package
zimbra-common-core-jar.x86_64
0:1.0.0.1522952748-1.r7<br>
>>>will be an update<br>
>>>---> Package
zimbra-mbox-conf.x86_64
0:1.0.0.1521707697-1.r7 will be<br>
>>>updated<br>
>>>---> Package
zimbra-mbox-conf.x86_64
0:1.0.0.1522952748-1.r7 will be<br>
>>>an update<br>
>>>---> Package
zimbra-mbox-service.x86_64
0:1.0.0.1521707697-1.r7 will<br>
>>>be updated<br>
>>>---> Package
zimbra-mbox-service.x86_64
0:1.0.0.1522952748-1.r7 will<br>
>>>be an update<br>
>>>---> Package
zimbra-mbox-war.x86_64 0:1.0.0.1521707697-1.r7
will be<br>
>>>updated<br>
>>>---> Package
zimbra-mbox-war.x86_64 0:1.0.0.1522952748-1.r7
will be <br>
>>>an<br>
>>>update<br>
>>>---> Package
zimbra-mbox-webclient-war.x86_64
0:1.0.0.1521723166-1.r7<br>
>>>will be updated<br>
>>>---> Package
zimbra-mbox-webclient-war.x86_64
0:1.0.0.1523095946-1.r7<br>
>>>will be an update<br>
>>>---> Package zimbra-talk.x86_64
0:1.0.3.1523266296-1.r7 will be <br>
>>>obsoleting<br>
>>>--> Processing Dependency:
zimbra-network-modules-ng >= 1.0.14 for<br>
>>>package:
zimbra-talk-1.0.3.1523266296-1.r7.x86_64<br>
>>>--> Running transaction check<br>
>>>---> Package
zimbra-network-modules-ng.x86_64 <br>
>>>0:1.0.14.1522918190-1.r7<br>
>>>will be installed<br>
>>>--> Processing Dependency:
zimbra-network-store >= 8.8.8 for package:<br>
>>>zimbra-network-modules-ng-1.0.14.1522918190-1.r7.x86_64<br>
>>>--> Finished Dependency
Resolution<br>
>>>*Error: Package:<br>
>>>zimbra-network-modules-ng-1.0.14.1522918190-1.r7.x86_64<br>
>>>(zimbra-888-patch)*<br>
>>>* Requires:
zimbra-network-store >= 8.8.8*<br>
>>>You could try using --skip-broken
to work around the problem<br>
>>>You could try running: rpm -Va
--nofiles --nodigest<br>
>>><br>
>>>[root@zimbra1 ~]# su zimbra<br>
>>>[zimbra@zimbra1 root]$ zmcontrol
-v<br>
>>>Release
8.8.8_GA_2009.RHEL7_64_20180322150747 RHEL7_64
FOSS edition.<br>
>>><br>
>>>This is a FOSS only server, and
should not fetch<br>
>>>*zimbra-network-modules-ng.*<br>
>>><br>
>>><br>
>>>Funny thing is, that on a FOSS
server with Zextras installed, it does<br>
>>>work:<br>
>>>[root@mail ~]# yum update -y<br>
>>>Loaded plugins: fastestmirror<br>
>>>Loading mirror speeds from cached
hostfile<br>
>>>* base: <a
href="http://mirrors.centos.webair.com"
moz-do-not-send="true">mirrors.centos.webair.com</a><br>
>>>* epel: <a
href="http://mirror.math.princeton.edu"
moz-do-not-send="true">mirror.math.princeton.edu</a><br>
>>>* extras: <a
href="http://mirrors.centos.webair.com"
moz-do-not-send="true">mirrors.centos.webair.com</a><br>
>>>* updates: <a
href="http://mirrors.tripadvisor.com"
moz-do-not-send="true">mirrors.tripadvisor.com</a><br>
>>>Resolving Dependencies<br>
>>>--> Running transaction check<br>
>>>---> Package
zimbra-common-core-jar.x86_64
0:1.0.0.1521707697-1.r7<br>
>>>will be updated<br>
>>>---> Package
zimbra-common-core-jar.x86_64
0:1.0.0.1522952748-1.r7<br>
>>>will be an update<br>
>>>---> Package
zimbra-mbox-conf.x86_64
0:1.0.0.1521707697-1.r7 will be<br>
>>>updated<br>
>>>---> Package
zimbra-mbox-conf.x86_64
0:1.0.0.1522952748-1.r7 will be<br>
>>>an update<br>
>>>---> Package
zimbra-mbox-service.x86_64
0:1.0.0.1521707697-1.r7 will<br>
>>>be updated<br>
>>>---> Package
zimbra-mbox-service.x86_64
0:1.0.0.1522952748-1.r7 will<br>
>>>be an update<br>
>>>---> Package
zimbra-mbox-war.x86_64 0:1.0.0.1521707697-1.r7
will be<br>
>>>updated<br>
>>>---> Package
zimbra-mbox-war.x86_64 0:1.0.0.1522952748-1.r7
will be <br>
>>>an<br>
>>>update<br>
>>>---> Package
zimbra-mbox-webclient-war.x86_64
0:1.0.0.1521723166-1.r7<br>
>>>will be updated<br>
>>>---> Package
zimbra-mbox-webclient-war.x86_64
0:1.0.0.1523095946-1.r7<br>
>>>will be an update<br>
>>>--> Finished Dependency
Resolution<br>
>>><br>
>>>Dependencies Resolved<br>
>>><br>
>>>================================================================================<br>
>>>Package Arch
Version Repository Size<br>
>>>================================================================================<br>
>>>Updating:<br>
>>>zimbra-common-core-jar x86_64
1.0.0.1522952748-1.r7<br>
>>>zimbra-888-patch 13 M<br>
>>>zimbra-mbox-conf x86_64
1.0.0.1522952748-1.r7<br>
>>>zimbra-888-patch 35 k<br>
>>>zimbra-mbox-service x86_64
1.0.0.1522952748-1.r7<br>
>>>zimbra-888-patch 3.7 k<br>
>>>zimbra-mbox-war x86_64
1.0.0.1522952748-1.r7<br>
>>>zimbra-888-patch 21 M<br>
>>>zimbra-mbox-webclient-war x86_64
1.0.0.1523095946-1.r7<br>
>>>zimbra-888-patch 24 M<br>
>>><br>
>>>Transaction Summary<br>
>>>================================================================================<br>
>>>Upgrade 5 Packages<br>
>>><br>
>>>Total download size: 59 M<br>
>>>Downloading packages:<br>
>>>Delta RPMs disabled because
/usr/bin/applydeltarpm not installed.<br>
>>>(1/5):
zimbra-mbox-conf-1.0.0.1522952748-1.r7.x86_64.rpm
| 35 kB<br>
>>>00:00<br>
>>>(2/5):
zimbra-mbox-service-1.0.0.1522952748-1.r7.x86_64.rp
| 3.7 kB<br>
>>>00:00<br>
>>>(3/5):
zimbra-common-core-jar-1.0.0.1522952748-1.r7.x86_64
| 13 MB<br>
>>>00:01<br>
>>>(4/5):
zimbra-mbox-war-1.0.0.1522952748-1.r7.x86_64.rpm
| 21 MB<br>
>>>00:02<br>
>>>(5/5):
zimbra-mbox-webclient-war-1.0.0.1523095946-1.r7.x86
| 24 MB<br>
>>>00:02<br>
>>>--------------------------------------------------------------------------------<br>
>>>Total 13 MB/s | 59 MB 00:04<br>
>>>Running transaction check<br>
>>>Running transaction test<br>
>>>Transaction test succeeded<br>
>>>Running transaction<br>
>>>Warning: RPMDB altered outside of
yum.<br>
>>> Updating :
zimbra-common-core-jar-1.0.0.1522952748-1.r7.x86_64
<br>
>>>1/10<br>
>>> Updating :
zimbra-mbox-war-1.0.0.1522952748-1.r7.x86_64
2/10<br>
>>> Updating :
zimbra-mbox-conf-1.0.0.1522952748-1.r7.x86_64
3/10<br>
>>> Updating :
zimbra-mbox-service-1.0.0.1522952748-1.r7.x86_64
4/10<br>
>>> Updating :
zimbra-mbox-webclient-war-1.0.0.1523095946-1.r7.x86_64<br>
>>> 5/10<br>
>>> Cleanup :
zimbra-mbox-service-1.0.0.1521707697-1.r7.x86_64
6/10<br>
>>> Cleanup :
zimbra-mbox-war-1.0.0.1521707697-1.r7.x86_64
7/10<br>
>>> Cleanup :
zimbra-mbox-conf-1.0.0.1521707697-1.r7.x86_64
8/10<br>
>>> Cleanup :
zimbra-common-core-jar-1.0.0.1521707697-1.r7.x86_64
<br>
>>>9/10<br>
>>> Cleanup :
zimbra-mbox-webclient-war-1.0.0.1521723166-1.r7.x86_64<br>
>>>10/10<br>
>>> Verifying :
zimbra-mbox-conf-1.0.0.1522952748-1.r7.x86_64
1/10<br>
>>> Verifying :
zimbra-mbox-war-1.0.0.1522952748-1.r7.x86_64
2/10<br>
>>> Verifying :
zimbra-mbox-service-1.0.0.1522952748-1.r7.x86_64
3/10<br>
>>> Verifying :
zimbra-mbox-webclient-war-1.0.0.1523095946-1.r7.x86_64<br>
>>> 4/10<br>
>>> Verifying :
zimbra-common-core-jar-1.0.0.1522952748-1.r7.x86_64
<br>
>>>5/10<br>
>>> Verifying :
zimbra-mbox-webclient-war-1.0.0.1521723166-1.r7.x86_64<br>
>>> 6/10<br>
>>> Verifying :
zimbra-mbox-war-1.0.0.1521707697-1.r7.x86_64
7/10<br>
>>> Verifying :
zimbra-mbox-service-1.0.0.1521707697-1.r7.x86_64
8/10<br>
>>> Verifying :
zimbra-common-core-jar-1.0.0.1521707697-1.r7.x86_64
<br>
>>>9/10<br>
>>> Verifying :
zimbra-mbox-conf-1.0.0.1521707697-1.r7.x86_64
10/10<br>
>>><br>
>>>Updated:<br>
>>> zimbra-common-core-jar.x86_64
0:1.0.0.1522952748-1.r7<br>
>>> zimbra-mbox-conf.x86_64
0:1.0.0.1522952748-1.r7<br>
>>> zimbra-mbox-service.x86_64
0:1.0.0.1522952748-1.r7<br>
>>> zimbra-mbox-war.x86_64
0:1.0.0.1522952748-1.r7<br>
>>> zimbra-mbox-webclient-war.x86_64
0:1.0.0.1523095946-1.r7<br>
>>><br>
>>>Complete!<br>
>>>[root@mail ~]# su zimbra<br>
>>>[zimbra@mail root]$ zmcontrol
restart<br>
>>><br>
>>>Good thing it's Friday!<br>
>>><br>
>>>Kind regards,<br>
>>><br>
>>>Barry de Graaff<br>
>>>Zeta Alliance<br>
>>>Co-founder & Developer<br>
>>><a href="http://zetalliance.org"
moz-do-not-send="true">zetalliance.org</a> |
<a href="http://github.com/Zimbra-Community"
moz-do-not-send="true">github.com/Zimbra-Community</a><br>
>>><br>
>>>+31 617 220 227 | skype:
barrydegraaff.tk<br>
>>>Fingerprint:
97f4694a1d9aedad012533db725ddd156d36a2d0<br>
>>><br>
>>>------------------------------------------------------------------------<br>
>>>*From: *"L Mark Stone" <a
class="moz-txt-link-rfc2396E"
href="mailto:lmstone@lmstone.com"
moz-do-not-send="true"><lmstone@lmstone.com></a><br>
>>>*To: *"Randy Leiker" <a
class="moz-txt-link-rfc2396E"
href="mailto:randy@skywaynetworks.com"
moz-do-not-send="true"><randy@skywaynetworks.com></a>,<br>
>>><a
class="moz-txt-link-abbreviated"
href="mailto:users@lists.zetalliance.org"
moz-do-not-send="true">users@lists.zetalliance.org</a>,
"Tony Publiski" <a
class="moz-txt-link-rfc2396E"
href="mailto:tonster@tonster.com"
moz-do-not-send="true"><tonster@tonster.com></a><br>
>>>*Sent: *Friday, April 13, 2018
2:03:48 AM<br>
>>>*Subject: *Re: [Users] Zimbra
8.8.8 Patch 1 release<br>
>>><br>
>>>On a single Zimbra 8.8.8 server, a
number of the Zimbra packages <br>
>>>today<br>
>>>were given updates that I
installed prior to installing the patch, <br>
>>>FWIW.<br>
>>><br>
>>><br>
>>>Not sure how/if they are
connected?<br>
>>><br>
>>><br>
>>> Start-Date: 2018-04-1218:40:46<br>
>>><br>
>>> Commandline: apt-get
dist-upgrade<br>
>>><br>
>>> Upgrade:
zimbra-mbox-service:amd64
(1.0.0.1521707697-1.u16,<br>
>>> 1.0.0.1522952748-1.u16),
plymouth-theme-ubuntu-text:amd64<br>
>>> (0.9.2-3ubuntu13.3,
0.9.2-3ubuntu13.4), zimbra-mbox-conf:amd64<br>
>>> (1.0.0.1521707697-1.u16,
1.0.0.1522952748-1.u16),<br>
>>> libplymouth4:amd64
(0.9.2-3ubuntu13.3, 0.9.2-3ubuntu13.4),<br>
>>> apport:amd64
(2.20.1-0ubuntu2.15, 2.20.1-0ubuntu2.16),<br>
>>> zimbra-talk:amd64
(1.0.2.1521642559-1.u16,<br>
>>> 1.0.3.1523266296-1.u16),
python3-apport:amd64 (2.20.1-0ubuntu2.15,<br>
>>> 2.20.1-0ubuntu2.16),
zimbra-mbox-war:amd64<br>
>>> (1.0.0.1521707697-1.u16,
1.0.0.1522952748-1.u16), plymouth:amd64<br>
>>> (0.9.2-3ubuntu13.3,
0.9.2-3ubuntu13.4),<br>
>>> zimbra-common-core-jar:amd64
(1.0.0.1521707697-1.u16,<br>
>>> 1.0.0.1522952748-1.u16),
zimbra-network-modules-ng:amd64<br>
>>> (1.0.13+1521603981-1.u16,
1.0.14.1522918190-1.u16),<br>
>>> python3-problem-report:amd64
(2.20.1-0ubuntu2.15,<br>
>>> 2.20.1-0ubuntu2.16),
zimbra-mbox-webclient-war:amd64<br>
>>> (1.0.0.1521723166-1.u16,
1.0.0.1523095946-1.u16)<br>
>>><br>
>>> End-Date: 2018-04-1218:41:17<br>
>>><br>
>>><br>
>>> Start-Date: 2018-04-1218:44:25<br>
>>><br>
>>> Commandline: apt-get install
zimbra-patch<br>
>>><br>
>>> Install: zimbra-patch:amd64
(8.8.8.1.1522961836-1.u16)<br>
>>><br>
>>> End-Date: 2018-04-1218:44:32<br>
>>><br>
>>><br>
>>><br>
>>>*_________________________________________________*<br>
>>><br>
>>>*Another Message From... L. Mark
Stone*<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>>------------------------------------------------------------------------<br>
>>>*From:* Users <a
class="moz-txt-link-rfc2396E"
href="mailto:users-bounces@lists.zetalliance.org"
moz-do-not-send="true"><users-bounces@lists.zetalliance.org></a>
on behalf of Tony<br>
>>>Publiski <a
class="moz-txt-link-rfc2396E"
href="mailto:tonster@tonster.com"
moz-do-not-send="true"><tonster@tonster.com></a><br>
>>>*Sent:* Thursday, April 12, 2018
7:09 PM<br>
>>>*To:* Randy Leiker; <a
class="moz-txt-link-abbreviated"
href="mailto:users@lists.zetalliance.org"
moz-do-not-send="true">users@lists.zetalliance.org</a><br>
>>>*Subject:* Re: [Users] Zimbra
8.8.8 Patch 1 release<br>
>>>I haven't actually looked at
what's fixed in this patch, however<br>
>>>*most* of the time you don't need
to ever patch anything but the <br>
>>>store<br>
>>>server, so really I wouldn't even
both with the other nodes. Yes, the<br>
>>>zimbra-common-core-jar package is
used by zmprov, and thus exists on<br>
>>>all nodes, however it's almost
certain that nothing patched affects<br>
>>>the non-mailbox server nodes. The
former patch would, of course, run<br>
>>>on all nodes, but only actually
copied files based on what services<br>
>>>were installed, and I can't
remember a patch I was involved in<br>
>>>actually patching anything on
non-store nodes.<br>
>>><br>
>>>Tony<br>
>>><br>
>>>------ Original Message ------<br>
>>>From: "Randy Leiker" <<a
class="moz-txt-link-abbreviated"
href="mailto:randy@skywaynetworks.com"
moz-do-not-send="true">randy@skywaynetworks.com</a><br>
>>><<a
href="mailto:randy@skywaynetworks.com"
moz-do-not-send="true">mailto:randy@skywaynetworks.com</a>>><br>
>>>To: <a
class="moz-txt-link-abbreviated"
href="mailto:users@lists.zetalliance.org"
moz-do-not-send="true">users@lists.zetalliance.org</a>
<<a
href="mailto:users@lists.zetalliance.org"
moz-do-not-send="true">mailto:users@lists.zetalliance.org</a>><br>
>>>Sent: 4/12/2018 7:03:31 PM<br>
>>>Subject: [Users] Zimbra 8.8.8
Patch 1 release<br>
>>><br>
>>> Hi Everyone,<br>
>>><br>
>>> Today Zimbra 8.8.8 Patch 1 was
released as GA:<br>
>>><a
href="https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.8/P1"
moz-do-not-send="true">https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.8/P1</a><br>
>>><br>
>>> One of the bug fixes included
(35115) helps with the Zimbra High<br>
>>> Availability open source
project I've been working on developing.<br>
>>> I'll be publishing the
initial reference designs for that project<br>
>>> very soon on its own web
site. In the meantime, I deployed 8.8.8<br>
>>> patch 1 to begin testing in my
lab environment which is running<br>
>>> CentOS 7, with ZCS 8.8.8. The
install instructions as written in<br>
>>> the release notes for Red
Hat/CentOS servers<br>
>>> <br>
>>>(<a
href="https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.8/P1#Install_the_Patch"
moz-do-not-send="true">https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.8/P1#Install_the_Patch</a>)<br>
>>> work fine if you're running a
single server install of ZCS. But,<br>
>>> if you're running a multi-node
install of ZCS, the patch install<br>
>>> instructions in the release
notes are inaccurate.<br>
>>><br>
>>> In my lab environment, I have
the following ZCS nodes provisioned:<br>
>>><br>
>>> * 2 x LDAP MMR nodes<br>
>>> * 2 x MTA nodes<br>
>>> * 2 x Proxy nodes<br>
>>> * 2 x Mailbox nodes<br>
>>><br>
>>> If you attempt to follow the
install instructions for the patch<br>
>>> with a similar ZCS multi-node
environment as noted above, you'll<br>
>>> see a dependency failure in
Yum that will prevent the patch from<br>
>>> installing:<br>
>>><br>
>>> Error: Package:
zimbra-patch-8.8.8.1.1522961836-1.r7.x86_64<br>
>>> (zimbra-888-patch)<br>
>>> Requires:
zimbra-store >= 8.8.8<br>
>>> You could try using
--skip-broken to work around the problem<br>
>>> You could try running: rpm
-Va --nofiles --nodigest<br>
>>><br>
>>> This occurs because the
zimbra-store package isn't installed on<br>
>>> all of the ZCS nodes.
Instead, what you'll need to do is on your<br>
>>> LDAP, MTA, and Proxy nodes, or
essentially any ZCS node where the<br>
>>> zimbra-store package is NOT
installed, simply run these commands:<br>
>>><br>
>>> * As the root user:<br>
>>> o yum upgrade (upgrades
the zimbra-common-core-jar package)<br>
>>> * As the zimbra user:<br>
>>> o zmcontrol restart<br>
>>><br>
>>> Then, on your ZCS mailbox
nodes (where the zimbra-store package is<br>
>>> installed), follow the install
instructions as written in the<br>
>>> 8.8.8 Patch 1 release notes.<br>
>>><br>
>>> When you get to the section in
the release notes that advises <br>
>>>running:<br>
>>><br>
>>> * yum install
zimbra-network-modules-ng<br>
>>> * yum install zimbra-chat
OR yum install zimbra-talk<br>
>>><br>
>>> If you've already upgraded to
8.8.8, which would of course be the<br>
>>> case if you're trying to
install patch 1, the 8.8.8 install<br>
>>> process uninstalls the
zimbra-chat package & replaces it with<br>
>>> zimbra-talk, so you only need
to run:<br>
>>><br>
>>> * As the root user:<br>
>>> o yum install
zimbra-network-modules-ng<br>
>>> o yum install
zimbra-talk<br>
>>> * As the zimbra user:<br>
>>> o zmmailboxdctl restart<br>
>>><br>
>>> Otherwise, all of the ZCS
services appeared to start successfully<br>
>>> following the install of Patch
1. I wasn't able to test it within<br>
>>> my Zimbra lab environment, but
I suspect the Ubuntu install<br>
>>> instructions in the release
notes need a similar clarification for<br>
>>> multi-node ZCS installs.<br>
>>><br>
>>><br>
>>> Randy Leiker (<a
class="moz-txt-link-abbreviated"
href="mailto:randy@skywaynetworks.com"
moz-do-not-send="true">randy@skywaynetworks.com</a><br>
>>> <<a
href="mailto:randy@skywaynetworks.com"
moz-do-not-send="true">mailto:randy@skywaynetworks.com</a>>
)<br>
>>> Skyway Networks, LLC<br>
>>> 1.800.538.5334 / 913.663.3900
Ext. 100<br>
>>><a
href="https://www.skywaynetworks.com"
moz-do-not-send="true">https://www.skywaynetworks.com</a>
<<a href="http://www.skywaynetworks.com"
moz-do-not-send="true">http://www.skywaynetworks.com</a>><br>
>>><br>
>>><br>
<br>
</div>
</span></font></div>
</blockquote>
<br>
</div>
</blockquote>
</blockquote>
<br>
</div>
</blockquote>
</blockquote>
<br>
</body>
</html>