What should I do when Linux upgrades Glibc?

In the Linux system, the Glibc-2.7 version is required when installing the software, but the Glibc version is too low to be upgraded, which causes the system to crash. What is the cause? What should I do? The following small series will introduce you to the solution to the system crash when Linux upgrades Glibc.

phenomenon:

install HP hardware monitor (hpasmcli) Tip relies on Glibc-2.7, while the machine is Glibc-2.5, the upgrade seems to have Glibc, and unfortunately upgrade At the time, there were more dependencies. I thought it was very smooth when I installed hpasmcli on other servers. I thought of copying the glibc library files of other servers directly to the machine. The files involved are:

/lib /libc-2.5.so #32-bit system

/lib64/libc-2.5.so # 64-bit system

Because the server system I am operating is 64-bit, it is overriding /lib64 At the instant of the /libc-2.5.so file, a large number of kernel errors are reported on the screen as follows (where host refers to the server hostname):

Message from syslogd@ at Fri Apr 26 18:10:35 2013 . . . Host kernel: in6b rsp 00007fff8c0b8698 error 4 Message from syslogd@ at Fri Apr 26 18:10:35 2013 . . . Host kernel: init[1]: segfault at 0000000000000000 rip 00002b28b2052e6b rsp 00007fff8c0b8698 error 4 Message from syslogd@ at Fri Apr 26 18:10:35 2013 . . . Host last message repeated 17 times Message from syslogd@ at Fri Apr 26 18:10:35 2013 . . . Host kernel: init[1]: segfau6b rsp 00007fff8c0b8698 error 4 Message from syslogd@ at Fri Apr 26 18:10:35 2013 . . . Host kernel: init[16b rsp 00007fff8c0b8698 error 4

Then the system crashes and can no longer log in.

Emergencyly contact the server room to restart the server and inform that it cannot be started.

Hey, I personally caused the accident!

Important:

glibc is the libc library released by gnu, which is the c runtime library. Glibc is the lowest-level api in Linux, and almost any other runtime depends on glibc. In addition to encapsulating the system services provided by the Linux operating system, glibc itself provides many other implementations of the necessary functional services. Since glibc covers almost all of the standards that are common to UNIX, you can imagine that it is all-encompassing.

Upgrading Glibc's advice: Don't install Glibc on a running system, or it will cause a system crash. At a minimum, you should install the new Glibc to a separate directory to ensure that you are not overwriting the Glibc you are currently using. (I will cover the ignorance, hehe!)

Solution:

Go to the computer room, but fortunately I saved the original library file in the directory /lib before replacing (libc-2.5 .so.bak), use the Linux system disk to enter the "rescue mode", restore the two library files that have been replaced, restart the system;

The system starts normally and is handed over to other departments. Colleagues go to recover the data.

The above is the introduction of the solution to the system crash when Linux upgrades Glibc. The method is very simple. It is necessary to enter the rescue mode and restore the replaced library file back. If you are upgrading Glibc Not overwriting the original Glibc will not cause the system to crash.