Problem after Zimbra Upgrade

[jpsinacola]

Starting convertd...Failed.
Starting convertd.../opt/zimbra/httpd-2.2.17/bin/httpd: /lib64/libc.so.6: version `GLIBC_2.10' not found (required by /opt/zimbra/httpd-2.2.17/lib/libapr-1.so.0)
failed.

and

Starting spell...Failed.
Starting apache.../opt/zimbra/httpd-2.2.17/bin/httpd: /lib64/libc.so.6: version `GLIBC_2.10' not found (required by /opt/zimbra/httpd-2.2.17/lib/libapr-1.so.0)
failed.


Both are looking for version GLIBC_2.10. I am running on SUSE Enterprise Server 11. Has anyone else had this problem or have a solution? WHen I do:

# rpm -q glibc
glibc-2.9-13.2

Does this mean I need to update my GLIBC to accomodate the latest version of Zimbra Network Edition, 6.10.6 (i believe this is correct). I am not sure how to update my GLIBC if that is what is required. Any hellp is appreciated.

[phoenix]

Originally Posted by andy21

It's ok I found a fix and the FAQ's

You found a fix for what? You haven't even asked a question nor given any information when requested.

[phoenix]

Originally Posted by jpsinacola

Does this mean I need to update my GLIBC to accomodate the latest version of Zimbra Network Edition, 6.10.6 (i believe this is correct). I am not sure how to update my GLIBC if that is what is required. Any hellp is appreciated.

Do I understand from your post that this error has occurred during an upgrade of Zimbr to 6.0.10 (that's the most recent version)?

[phoenix]

Originally Posted by andy21

Hey Bill,

Sorry didnt reply, new to the whole internet thing. I got it all sorted, I just needed to update. Thanks anyway.

How about updating your forum profile with the output of the following command (do not post the output in this thread):

zmcontrol -v

[jpsinacola]

Bill,

Yes, this occured during an update to the latest version 6.0.10. I have since tried to update SuSE, but the highlest level of GLIBC was glibc-2.9-13.11.1, which is what I am on now. After that update, I completely removed Zimbra, and reinstalled. Same errors. I removed it again and reverted back to 6.0.6, which is up right now. I will probably just wait until 7 comes out to upgrade again (fool me once). There is a SP1 available for SuSE, which I do not have installed, but I did not see anything in the update to 6.0.10 that would say, "Hey, watch out, you need GLIBC 2.10!", so that led me to believe I was doing something wrong. I would update my profile, but as I said, I reverted back to 6.0.6. Look, I am a Windows Server guy, a cycle I am trying to break, so I am fairly new with Linux. I bought a 150 user license pack for Zimbra and I want to migrate my Exchange 2003 server to Zimbra. So, that is what I am working on. The latest current version would be great. Thanks for the help Bill.

[phoenix]

Originally Posted by jpsinacola

There is a SP1 available for SuSE, which I do not have installed, but I did not see anything in the update to 6.0.10 that would say, "Hey, watch out, you need GLIBC 2.10!", so that led me to believe I was doing something wrong.

SP1 is a requirement for 6.0.9 upwards: Bug 52031 – SLES11_64 Network build : services failed to start due to GLIBC_2.10 not found. - it's also mentioned on P2 of the Release Notes.

[jpsinacola]

Blast. As much as I thought I looked I didn't see it. I looked briefly in the "Before you upgrade" section. Thanks for pointing out the fact that I hate to read and failed to plan. I'll get on installing SP1. Your assistance is appreciated.

[phoenix]

Originally Posted by jpsinacola

Blast. As much as I thought I looked I didn't see it. I looked briefly in the "Before you upgrade" section. Thanks for pointing out the fact that I hate to read and failed to plan.

Don't worry, everyone misses the one thing they should read in the Release Notes.

Originally Posted by jpsinacola

I'll get on installing SP1. Your assistance is appreciated.

You're welcome.

[LMStone]

There's a Novell post somewhere, but the trigger for all of this is Novell deciding to upgrade the kernel version in SLES11-SP1 from the version in SLES11-GA (SP0).

SUSE has never done this before with SLES to my knowledge (and I don't think Red Hat has done so either), so the article had Novell explaining that they were under great pressure to upgrade the kernel to have access to the hardware support, virtualization capabilities and other improvements in the later kernel. Novell claims they spent months talking with hardware vendors and ISVs to make sure that upgrading the kernel like that would not break any existing certifications. Oracle, HP, IBM etc. all said OK, so Novell pulled the trigger.

In the past, Novell back-ported security fixes and other features from later kernels into the SLES kernel, to give customers the benefits of later kernels but the stability of an ISV-certified system.

The article had Novell claiming that things like KVM functionality, support for ext4, btrfs and other in-demand features of the later kernel were not capable of being backported to the version of the kernel in SLES11-SP0.

Hope that helps!
Mark