Bug 695599
| Summary: | Internal error in yum | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter H. Jones <jones.peter.busi> | ||||
| Component: | yum | Assignee: | Seth Vidal <skvidal> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 15 | CC: | ffesti, james.antill, maxamillion, pmatilai, tim.lauridsen | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-04-12 12:49:10 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: | |||||||
| Attachments: |
|
||||||
After searching with Google, I rediscovered the rpm --rebuilddb command. That fixed up my RPM database. Whew! *** This bug has been marked as a duplicate of bug 672932 *** |
Created attachment 491414 [details] messages appearing in "Show Detail" in package kit update window Description of problem: Internal error in backend Version-Release number of selected component (if applicable): Unknown. When I try to run yum, I get: "[root@localhost jones]# yum --help error: rpmdb: Thread/process 1704/140150790620960 failed: Thread died in Berkeley DB library error: db4 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db4 - (-30974) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main: Error: rpmdb open failed " How reproducible: Always Steps to Reproduce: 1. Trying to install debug packages with Add/Remove software, because abrt was getting "operation not permitted" messages when trying to download debug info. 2. 3. Actual results: Can't open rpmdb. Would like to know if I can get it back without reinstalling whole system. Expected results: Normal bug reporting Additional info: