Bug 218672 - Corruption of yum database whilst installing eclipse-platform package
Summary: Corruption of yum database whilst installing eclipse-platform package
Keywords:
Status: CLOSED DUPLICATE of bug 218666
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: yum
Version: 5.0
Hardware: i386
OS: Linux
medium
urgent
Target Milestone: ---
: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-06 18:20 UTC by Paolo De Nictolis
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-12-06 18:26:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Corruption of yum database (170.33 KB, image/png)
2006-12-06 18:20 UTC, Paolo De Nictolis 		no flags Details
rpmdb PANIC error launching yum after database corruption (1.10 KB, text/plain)
2006-12-06 18:23 UTC, Paolo De Nictolis 		no flags Details
View All

Description Paolo De Nictolis 2006-12-06 18:20:06 UTC 
Description of problem: I had finally downloaded eclipse-platform with related
packages (see bug 218666) and yum was installing packages, after "Transaction
Succeeded", when yum database were corrupted (see attached pic). Now, launching
yum, I've a recurrent PANIC error in rpmdb (see attached text trace).


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Paolo De Nictolis 2006-12-06 18:20:06 UTC 
Created attachment 142973 [details]
Corruption of yum database
Comment 2 Paolo De Nictolis 2006-12-06 18:23:07 UTC 
Created attachment 142974 [details]
rpmdb PANIC error launching yum after database corruption
Comment 3 Jeremy Katz 2006-12-06 18:26:03 UTC 

*** This bug has been marked as a duplicate of 218666 ***

*** This bug has been marked as a duplicate of 218666 ***
Comment 4 Paolo De Nictolis 2006-12-06 21:51:14 UTC 
Problem is solved (temporary, since problem presehents each two-three times rpm
runs) cleaning up lock state information in the RPM db, using

rm -f /var/lib/rpm/__db*
Note You need to log in before you can comment on or make changes to this bug.