Bug 87681
Summary: | rpm and up2date not working | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Eric Gibson <ericgibson> |
Component: | rpm | Assignee: | Paul Nasrat <nobody+pnasrat> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | lists |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-19 19:10:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eric Gibson
2003-04-01 07:43:22 UTC
Does rpm from the command line work? Try rpm -qa and/or rpm --rebuilddb -vv If that doesn't produce output, then probably rm -f /var/lib/rpm/__db* is the fix (i.e. removing stale locks). Does the above "work"? (up2date problem next) The command line DOES work. And I can rebuild the database, expect the list is only partial (rpms loaded/ reloaded since this problem first occured). I have run (and rerun) all of the "fixes" you gave me and the problem does not totally clear. Removing the stale locks do nothing and when I rebuild the database, the locks reoccur __db.001, __db.002, and __db.003. The GUI Package manager still fails to load is list of packages. It crashes and gives me and "Unknown Error" mssg. up2date still not functioning in any capacity. Yes, the locks are in the files, not the files themselves. Good, rpm works from the CLI. Next step is to verify packages involved. Try rpm -V rpm up2date python glibc to insure that the packages are installed correctly. (next will be to verify up2date functionality) glibc is not showing up as present (even though I KNOW it's there), sent I have not reloaded the rpm since the problem started. I will reload that rpm and update you to see if the problem is corrected. I am seeing this problem also. (The only difference for me is that I'm using 7.3) rpm claims some packages exist, and others don't (even though they are clearly there.) For example, [matt@lightnin rpm]$ rpm -q redhat-release redhat-release-7.3-1 [matt@lightnin rpm]$ rpm -q rpm package rpm is not installed [matt@lightnin rpm]$ rpm -q kernel package kernel is not installed Obviously, rpm is installed. Most packages seem to have disappeared, according to rpm. rpm --rebuilddb makes no difference. Running up2date on the command line gives the same error reported above ("Couldn't determine what version of rpm you are running.") I've tried the tips above. rpm -qa works, but the listing is very incomplete. There's no obvious reason why some packages are reported as installed, and others aren't. Verifying python fails, but I presume that's because rpm reckons glibc isn't installed (obviously, it is). [matt@lightnin rpm]$ rpm -V rpm up2date python glibc package rpm is not installed package up2date is not installed Unsatisfied dependencies for python-1.5.2-43.73: /bin/sh , libcrypto.so.2 , libcrypt.so.1 , libcrypt.so.1(GLIBC_2.0) , libc.so.6 , libc.so.6(GLIBC_2.0) , libc.so.6(GLIBC_2.1) , libc.so.6(GLIBC_2.1.2) , libc.so.6(GLIBC_2.1.3) , libc.so.6(GLIBC_2.2) , libdl.so.2 , libdl.so.2(GLIBC_2.0) , libdl.so.2(GLIBC_2.1) , libgmp.so.3 , libm.so.6 , libm.so.6(GLIBC_2.0) , libnsl.so.1 , libnsl.so.1(GLIBC_2.0) , libpthread.so.0 , libpthread.so.0(GLIBC_2.0) , libpthread.so.0(GLIBC_2.1) , libssl.so.2 , libz.so.1 package glibc is not installed I've done a pretty comprehensive Google search and turned up a few people having this problem, but no solutions. At this stage I'm tempted to deinstall and reinstall rpm, but I'd rather locate the problem. I had similar error "Could not determine what version of Red Hat Linux you are running" (linked to rpm -V redhat-release coming up null). moved /var/lib/rpm/__* to /old rpm --rebuilddb db_verify Packages got the error specified here: http://www.rpm.org/hintskinks/repairdb/ followed those instructions, and got it to work. |