Record the lessons learned when upgrading gblic in centos, centosgblic

Record the lessons learned when upgrading gblic in centos, centosgblic

A few days ago, the company's project needed to watermark the uploaded images. angularjs was used at the front end, nodejs was used at the back end, and a search on the Internet found an images library. I tried it well in a local Windows environment, then I uploaded the test server (centos6.5 system), and the result went wrong. I checked it online and found that gblic2.14 was required (centos6.5 comes with version 2.12.

Later, I looked at the plug-in and thought it was relatively simple and easy to use. Haha, I decided to upgrade gblic2.12. After reading the plug-in, I upgraded it to 2.15 based on the principle that it would be enough, the local Virtual Machine centos6.5 has been tried for a while, and it is OK. After the test server is upgraded, the result will be an error. If the ssh remote connection fails, the system will crash, later, two people reinstalled the system and spent two days on it. Lessons learned...

Upgrade reference Tutorial: http://blog.csdn.net/officercat/article/details/39520227 (ps: Error in personal reasons, blog article is still very good ).

The main cause of the system crash is that the installation error is not handled rashly, and the lack of experience in handling errors in less than two months from linux directly reflects the handling:

Error: After the installation fails, you should actually point the soft connection back,

Ln-s/lib64/libc-2.15.so lib64/libc. so.6

However, the fact is that I did not point out the window with root permissions (the two windows opened at the time), and then the su sudo command in the other window all invalidated me, the remote connection is also rejected by the server and cannot be logged on to the system ...., to modify the soft connection, rm-rf/lib64/libc is required. so.6, however, it is a tragedy if you do not have the permissions, so the endless loop is not saved );

Then, the last login window cannot solve the problem, and then quit directly,

 

Remember this lesson and be cautious in the future. It is difficult for you to reinstall the system environment and complete the configurations .......