version GLIBC_2.3 not found when starting Apache

proco · 09-22-2006, 10:42 AM

I am trying to upgrade our test server to apache 2.0.50 and tomcat 5.0.28. Rather than overwrite our existing installation, I did a new installation. I downloaded the mod_jk connector and followed the configuration instructions I have for our app and when I try to start apache I get multiple versions of the following error:

Quote:

Cannot load /usr/local/apache2/modules/mod_rewrite.so into server: /lib/i686/libc.so.6: version `GLIBC_2.3' not found (required by /usr/local/apache2/modules/mod_rewrite.so)

I ran strings /lib/libc.so.6 | grep GLIBC and there was no listing for GLIBC_2.3. So it looks like I need to upgrade my glibc package.

My problem is figuring out which version will work for me. Our server is running Red Hat 7.2 (kernel version 2.4.20-28.7). The version of glibc we have is glibc-2.2.4-33.

I'm totally new to Linux & webserver setup, so any help would be greatly appreciated.

Thanks!
Mike

Lenard · 09-22-2006, 12:04 PM

Step one: Install a supported version of Red Hat Linux on your test server.

Red Hat and just about everybody else in the world has stopped supporting RHL7.2 a long time ago (nearly three years ago for Red Hat). CentOS and Scientific Linux are both freely available binary compatible equivalents of RHEL which are freely available for download/purchase. The Fedora Core series is the replacement for the old RHL series the current version 5 can be consider as RHL14 and Fedora Core 6 (the next version) is due out shortly (October 11, 2006 is the scheduled release date).

Warning upgrading glibc can cause and has caused major problems for many, it can be done but you really, really need to carefully plan and check everything. To give yourself an idea about possible damage as root test remove glibc;

rpm -e glibc glibc-common --test

proco · 09-22-2006, 03:11 PM

Quote:

Originally Posted by Lenard

Step one: Install a supported version of Red Hat Linux on your test server.

Red Hat and just about everybody else in the world has stopped supporting RHL7.2 a long time ago (nearly three years ago for Red Hat).

This is what I was afraid of. Thanks for the help. Looks like we'll be trying to serve up our app upgrade with our existing apache/tomcat configuration until management decides on what version we should be using.

Thanks again.

Lenard · 09-23-2006, 06:08 AM

The most direct upgrade path is to install one of the distros based on RHEL 3. CentOS, Scientific Linux and Whitebox Linux come to mind, should really consider going the RHEL 4 compatible path however.

The RHEL 3 family is based from the RHL9/FC1 releases, currenty the glibc rpm version is glibc-2.3.2-95.44.i686.rpm for example. And you should be able to upgrade from RHL7.2 to CentOS 3.8 without a problem. it is always advisable to make a backup (tested of course) just in case. Since you made refererence to a 'test server' give it a try.