Kbase 21239: What glibc Version Is Needed in RedHat Linux 7.0
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/06/2009 |
|
Status: Verified
GOAL:
What is the impact of having an old glibc library in Red Hat Linux 7.0.
FACT(s) (Environment):
RedHat Linux 7.0
Progress 9.1D
FIX:
The glibc package is one of the most important packages in Linux. Without this package the whole system wouldn't work at all. In the case of Progress, when we start up any services or any database using the SQL-92 interface, we use some libraries included in this package. Given that Linux is changing very fast, it is possible that our distribution has an old version of this package. This situation could cause several runtime errors that are difficult to trace since this is not Progress code but Linux code.
Possible errors range from errors reported in the log file up to core files and unexpected Server shutdowns. To avoid this kind of problem, verify what version of this package you have, and if the package is outdated then download a more recent version from the Internet. Apply it to your system before you start up any Progress process.
To find out the version of this package that you have, use the following command:
# rpm -qa | grep glibc
rpm is the Red Hat Package Manager and is fully documented in the Red Hat manuals.
The result should look similar to this :
glibc-2.1.92-14
glibc-devel-2.1.92-14
glibc-common-2.1.92-12
In this case you have an outdated glibc package so you need to update to a 2.2x version. Updating these packages probably won't be easy since they have dependencies among them, however rpm let us bypass these dependencies so we can upgrade the packages safely. To upgrade the packages, get them from your Linux distributor, in this case www.redhat.com. Search for 'glibc i386' which will then show you glibc for both V6 and V7. Choose the V7.0 one. Once you have downloaded these files, you should complete the following instructions:
# rpm --nodeps -U glibc-common-2.2.12
# rpm --nodeps -U glibc-2.2.12
# rpm --nodeps -U glibc-devel-2.2.12
This will update the libraries to the correct version. Once you've completed these steps you can bring up all the Progress services and databases, and the environment should be much more stable.