Install on older zimbra

This is the area for a general support questions, discussions and information that you can read and share. Post your experiences, stats and tricks and tips that are not covered elsewhere. Remember, for questions please search the FAQ first, as your question may already be answered.

Moderators: wizard, magicspam

Post Reply
darvil
Posts: 1
Joined: Mon May 23, 2016 8:40 am

Install on older zimbra

Post by darvil » Mon May 23, 2016 9:37 am

Hi I didn't have any issues installing on the new zimbra 8.6 but recently I installed magic spam on a version 7 zimbra.

After that I get the following error

Error on update: [Fatal error executing remote url fetch. Exit code: [0]]

I found some old threads on solutions to this. Some of it point to a network issue but this definately isn't a network issue plus I made sure the firewall is disabled but still no go.

Can you guys make some suggestions on what I can do? Thanks.


Thanks

magicspam
Posts: 1037
Joined: Tue Oct 28, 2008 2:27 pm

Re: Install on older zimbra

Post by magicspam » Wed Jun 08, 2016 11:24 am

Just for everyone's information, this issue was resolved through email conversations, and the result is below:
We were able to confirmed this as being related to a bug that is currently
undergoing investigation on the CentOS platform. It appears that an errant
set of updates were released for CentOS 6.8 specific to cURL and libnss
operating within a XEN environment (something to do with XEN kernels
reporting incorrect CPU flags) that caused these issues to crop up
(apparently specific to a series of PKI encryption functions and TLSv1).

There is a long thread on the topic available at:

https://bugs.centos.org/view.php?id=10930&nbn=5

While there is a work around of exporting an environment variable such as
you have already done for the yum package, said environment variable will
be user / environment specific and as such the mileage will definitely vary
- in other words it could turn into a long long path of playing whack-a-mole
to get the variable set for all services.

At this time it is our current recommendation to 'downgrade' and lock the
curl packages in question. There seem to be some variances reported in the
thread (and more than a little confusion!) but we think the following should
do the trick:

NSS_DISABLE_HW_AES=1
yum downgrade curl libcurl
yum install yum-plugin-versionlock
yum versionlock curl libcurl

Hopefully this will help to resolve the issue and allow your MagicSpam
system to return to a fully functional state.
-- MagicSpam Support Team --

Post Reply

Return to “General Discussions and Support Questions”

Who is online

Users browsing this forum: No registered users and 1 guest