The fastest way to crash a Linux System

The fastest way to crash the Linux system-Linux Enterprise Application-Linux server application information. For more information, see the following. Source: IT expert network

Symptom:

When installing HP Hardware Monitoring (hpasmcli) prompts that you need to rely on the Glibc-2.7, and the local is the Glibc-2.5, it seems to have to upgrade Glibc, but unfortunately there are more dependencies during the upgrade, when we thought that hpasmcli was successfully installed on other servers, we thought that we could copy the glibc library files from other servers directly to the local machine. The files involved were:

/Lib/libc-2.5.so #32-bit System

/Lib64/libc-2.5.so #64-bit System

Because the server system I operate is 64-bit, a large number of Kernel errors are reported immediately on the screen at the moment of overwriting/lib64/libc-2.5.so files, as shown below (where host refers to the server host name ):

Message from syslogd @ at Fri Apr 26 18:10:35 2013... host kernel: in6b rsp 20177fff8c0b8698 error 4 Message from syslogd @ at Fri Apr 26 18:10:35 2013... host kernel: init [1]: segfault at 0000000000000000 rip %2b28b2052e6b rsp %7fff8c0b8698 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 route 7fff8c0b8698 error 4 Message from syslogd @ at Fri Apr 26 18:10:35 2013... host kernel: init [16b rsp 20177fff8c0b8698 error 4

Then the system crashes and cannot log on again.

Urgently contact the data center to restart the server and inform that the server cannot be started.

Ah, I personally caused this accident!

Key points:

Glibc is the libc library released by gnu, that is, the c Runtime Library. Glibc is the most underlying api in linux, and almost any other Runtime Library depends on glibc. Glibc not only encapsulates the system services provided by the linux operating system, but also provides implementation of many other necessary functional services. Because glibc covers almost all of the UNIX standard, it is conceivable that its content is all-encompassing.

Tips for upgrading Glibc: do not install Glibc on a running system. Otherwise, the system will crash. At least install the new Glibc in another separate directory, to ensure that the Glibc currently in use is not overwritten. (I will overwrite it with ignorance ,??)

Solution:

Rush to the machine room, fortunately I saved the original library file (libc-2.5.so.bak) under the directory/lib before the replacement, using the Linux system disk to enter the "rescue mode ", restore the two replaced library files and restart the system;

If the system is started normally, hand it over to colleagues from other departments to restore the data. (I will tell you that I am running a DB server !)