Bug 431236 - Error Updating after fresh install of Fedora Core 8
Summary: Error Updating after fresh install of Fedora Core 8
Alias: None
Product: Fedora
Classification: Fedora
Component: pirut
Version: 8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-02-01 17:19 UTC by SG-Austin
Modified: 2008-05-28 19:32 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2008-05-28 19:32:29 UTC

Attachments (Terms of Use)

Description SG-Austin 2008-02-01 17:19:35 UTC
Description of problem:

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

How reproducible:

Steps to Reproduce:
1.Installed fresh Fedora Core 8 from DVD, with no additional components, no Dev,
no Office, no web server
2. Had issue with Volari display driver so changed grub load to remove rhgb
quiet in run level 3
3. Started X
4. The very first time the system prompted for updates, it was not able to
update with the error
Actual results:
raceback (most recent call last):
  File "/usr/sbin/pup", line 614, in <module>
  File "/usr/sbin/pup", line 606, in main
    pup = PackageUpdater(not options.autoapply, options.config)
  File "/usr/sbin/pup", line 85, in __init__
    GraphicalYumBase.__init__(self, False, config)
  File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 129, in __init__
  File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 113, in
  File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 159, in _getConfig
    self._conf = config.readMainConfig(startupconf)
  File "/usr/lib/python2.5/site-packages/yum/config.py", line 613, in readMainConfig
    yumvars['releasever'] = _getsysver(startupconf.installroot,
  File "/usr/lib/python2.5/site-packages/yum/config.py", line 680, in _getsysver
    idx = ts.dbMatch('provides', distroverpkg)
TypeError: rpmdb open failed

Local variables in innermost frame:
installroot: /
ts: <rpmUtils.transaction.TransactionWrapper instance at 0x87d8dac>
distroverpkg: redhat-release

Expected results:
Should have started to reach out to download and install updates as it normally

Additional info:

Comment 1 Nicolas Large 2008-04-24 08:01:23 UTC
I've the same problem and I've tried to rebuilt rpmdb using "rpm --rebuilddb".
I've got the following : 

rpmdb: PANIC: fatal region error detected; run recovery
erreur: erreur db4(-30977) de dbenv->open: DB_RUNRECOVERY: Fatal error, run
database recovery
erreur: ne peut ouvrir l'index Packages en utilisant db3 -  (-30977)

Comment 2 Nicolas Large 2008-04-24 08:06:26 UTC
Finally I've just found a solution to fix this bug : 
doing : 

rm /var/lib/rpm/__db*
rpm --rebuilddb

I was able to fix this error. I don't know why or how it happened but it works.

Note You need to log in before you can comment on or make changes to this bug.