One of our CentOS servers has went into a strange state and is complaining that
libpython2.7.so.1.0 cannot open shared object files. Yum is unusable and other features are failing to function (such as sending mail from the system, SSH'ing to it etc.) I really don't want to have to rebuild the server from scratch and I'm hoping someone can advise on a fix for me.
An example of the error I am presented with when running Yum:
/usr/bin/python: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory
I cannot use the pipe symbol (as I am having to manage the system via VMware console) and I cannot copy text from this console either, so if you require me to run any commands I will have to type the results out manually.
Answers to the questions asked on Stack Overflow:
python into the CLI still works and opens Python (note the date/time stamp below is when this stopped working!):
Python 2.7.15 (default, Jun 18 2018, 08:40:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] on linux2 >>>
rpm --verify -a into the CLI returns the following:
$ rpm --verify -a rpm: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory