It's a bad idea to modify it.
During an upgrade, yum just overwrites it without notice and without creating any .rpmsave
Countless times I've found solutions on the net: I'll try to give back some, by sharing interesting things I'll come across.
Showing posts with label yum. Show all posts
Showing posts with label yum. Show all posts
2012-02-25
2011-12-23
libfipscheck
Another yum mess:
After an apparently successfull yum update, sshd didn't start with the following error message:
/usr/lib/libfipscheck.so.1: file too short
The file was 0 bytes.
Where does it come from?
the package was installed but somewhat corrupted, so I reinstalled it:
# yum reinstall fipscheck-lib
after that, sshd started fine.
After an apparently successfull yum update, sshd didn't start with the following error message:
/usr/lib/libfipscheck.so.1: file too short
The file was 0 bytes.
Where does it come from?
# yum provides libfipscheck.so.1
fipscheck-lib-1.2.0-1.el5.i386 : Library files for fipscheck
Repo : rhel-5.5-x86_64
Matched from:
Other : libfipscheck.so.1
Repo : rhel-5.5-x86_64
Matched from:
Other : libfipscheck.so.1
the package was installed but somewhat corrupted, so I reinstalled it:
# yum reinstall fipscheck-lib
after that, sshd started fine.
2011-12-22
Yum headaches
After a yum update on a workstation, I've found the root mailbox full of messages like this:
/etc/cron.daily/0logwatch:
The yum itself had problems:
# yum
I've reinstalled yum
rpm -iv yum-3.2.22-37.el5.noarch.rpm rpm-python-4.4.2.3-22.el5.i386.rpm rpm-4.4.2.3-22.el5.i386.rpm
and yum was back in action, but there were other problems:
with an rpm -qa I looked at the installed packages and they appeared to be less than usual.
For example there was no mkinitrd package installed but the mkinitrd command was right there.
Probably the rpm database was corrupted but an
# rpm --rebuilddb
sorted no different effect.
I did an rpm -qa on a similarly configured workstation and compared it with the rpm -qa of this machine: there were more than 140 rpms missing.
I extracted the missing list and reinstalled all of them with a big yum install command
...and 140 more...
/etc/cron.daily/0logwatch:
Undefined subroutine &main::TimeBuild called at /etc/cron.daily/0logwatch line 846.
}
{
The yum itself had problems:
# yum
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:
cannot import name RpmUtilsError
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, Apr 14 2011, 20:42:01)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-50)]
If you cannot solve this problem yourself, please go to
the yum faq at:
http://wiki.linux.duke.edu/YumFaq
I've reinstalled yum
rpm -iv yum-3.2.22-37.el5.noarch.rpm rpm-python-4.4.2.3-22.el5.i386.rpm rpm-4.4.2.3-22.el5.i386.rpm
rpm-apidocs-4.4.2.3-22.el5.i386.rpm rpm-build-4.4.2.3-22.el5.i386.rpm rpm-devel-4.4.2.3-22.el5.i386.rpm rpm-libs-4.4.2.3-22.el5.i386.rpm
and yum was back in action, but there were other problems:
with an rpm -qa I looked at the installed packages and they appeared to be less than usual.
For example there was no mkinitrd package installed but the mkinitrd command was right there.
Probably the rpm database was corrupted but an
# rpm --rebuilddb
sorted no different effect.
I did an rpm -qa on a similarly configured workstation and compared it with the rpm -qa of this machine: there were more than 140 rpms missing.
I extracted the missing list and reinstalled all of them with a big yum install command
# yum install \
NetworkManager \
NetworkManager-glib \
NetworkManager-gnome \
a2ps \
at-spi \
at-spi-devel \
autofs \
avahi \
avahi-compat-libdns_sd \...and 140 more...
Subscribe to:
Posts (Atom)