Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Hello everybody, It's my first post in this forums. i visited this website a lot before finding answers for different questions but this time i got a question which i could not find a topic for not in this website nor in the others.
i have a testing server (Centos 5.4) with cpanel installed, once i ran a script which erases log files by using the find and rm command.
anyway looks like this script deleted one of the modules to python, the logging module. so python stopped working, i thought reinstalling it should solve the problem so i downloaded the tar ball and reinstalled python from source and it's all the same.
now yum command isn't working because it's giving me this error "no module named logging".
i decided to synchronize the whole python folder /usr/lib/python2.4/ from the live server using rsync and it did not help
i searched for the yum rpm package and i downloaded and installed yum-3.2.22-20.el5.centos.src.rpm using rpm and it did not help.
so i don't know how could i solve this problem? or what am i missing here?
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:
No module named logging
Please install a package which provides this module, or
verify that the module is installed correctly.
It's possible that the above module doesn't match the
current version of Python, which is:
2.4.3 (#1, Sep 3 2009, 15:37:37)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-46)]
If you cannot solve this problem yourself, please go to
the yum faq at: