-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 13 Jan 2003 03:29:35 -0500, Justin F. Kuo wrote: > > Try running this as root: > > > > rpm -qa | xargs -n 1 -t rpm -V &> rpm-Va.txt > > less rpm-Va.txt > > > > It is the output of a verification of all your installed packages. > > The flags at the start of each line are explained in "man rpm" in > > the section "VERIFY OPTIONS". > > > > See how many files are missing and how many are listed as not having > > passed the MD5 checksum test, the '5' flag. Ignore some types of > > files, such as Python compiled files, font indices or some config > > files. > > > > I ran the rpm verification commands as suggested. > > [root@mango temp]# rpm -qa | xargs -n 1 -t rpm -V &> rpm-Va.txt > [root@mango temp]# less rpm-Va.txt > rpm -V glibc-2.2.93-5 > rpm -V gdbm-1.8.0-18 > rpm -V libacl-2.0.11-2 > rpm -V linc-0.5.2-2 > xargs: rpm: terminated by signal 11 > > It appears to have aborted. I may need to reinstall the RedHat OS. Is this reproducible? What does "rpm -V rpm" give? And "rpm --rebuilddb"? According to your logs, you had a kernel panic with 2.4.18-14 on January 5th and another one 20 minutes later. Any particular reason for that? In the logs I couldn't find any hard disk drive block read error messages. I suspect your RAM chips may be bad or your system unstable. That would explain the kernel panic and signal 11 upon running rpm, unless RPM itself is damaged. You might want to try memtest86 from Google. The fsck on January 7th corrected /home, not /usr or any partition that contains important system binaries. - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+IqTn0iMVcrivHFQRAi51AJ4wqc9XzDuRbPoCRcLiMq9UVylZ9ACfdhUp 8g/mFydnRD6T+M+2ugZ2rvg= =d/Lf -----END PGP SIGNATURE----- -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
