Bug 498341 - YUM gives fatal errors whenever run
Summary: YUM gives fatal errors whenever run
Keywords:
Status: CLOSED DUPLICATE of bug 495087
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 10
Hardware: i686
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-29 23:06 UTC by Rebecca Fine
Modified: 2014-01-21 23:09 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-05-04 14:38:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rebecca Fine 2009-04-29 23:06:25 UTC
Description of problem:

I can't update any software, the kernel, or yum itself. I can't run yum clean all, either. I get this when I try to run yum update:

# yum update
Loaded plugins: refresh-packagekit
rpmdb: Thread/process 2538/3087918784 failed: Thread died in Berkeley DB library
error: db4 error(-30975) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 -  (-30975)
error: cannot open Packages database in /var/lib/rpm
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 229, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 84, in main
    base.getOptionsConfig(args)
  File "/usr/share/yum-cli/cli.py", line 184, in getOptionsConfig
    enabled_plugins=self.optparser._splitArg(opts.enableplugins))
  File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 192, in _getConfig
    self._conf = config.readMainConfig(startupconf)
  File "/usr/lib/python2.5/site-packages/yum/config.py", line 774, in readMainConfig
    yumvars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg)
  File "/usr/lib/python2.5/site-packages/yum/config.py", line 844, in _getsysver
    idx = ts.dbMatch('provides', distroverpkg)
TypeError: rpmdb open failed


I get this when I try to run yum clean all:

# yum clean all
Loaded plugins: refresh-packagekit
rpmdb: Thread/process 2538/3087918784 failed: Thread died in Berkeley DB library
error: db4 error(-30975) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 -  (-30975)
error: cannot open Packages database in /var/lib/rpm
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 229, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 84, in main
    base.getOptionsConfig(args)
  File "/usr/share/yum-cli/cli.py", line 184, in getOptionsConfig
    enabled_plugins=self.optparser._splitArg(opts.enableplugins))
  File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 192, in _getConfig
    self._conf = config.readMainConfig(startupconf)
  File "/usr/lib/python2.5/site-packages/yum/config.py", line 774, in readMainConfig
    yumvars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg)
  File "/usr/lib/python2.5/site-packages/yum/config.py", line 844, in _getsysver
    idx = ts.dbMatch('provides', distroverpkg)
TypeError: rpmdb open failed



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

I can't figure out which version (YUM errors whenever I try), but I successfully updated everything a few days to a week ago via the Package Manager, so it should be pretty recent.


How reproducible:
This happens every time I try to update via either the Package Manager or YUM.

Steps to Reproduce:
1. Run the Package Manager (System Updater) and wait till the service tries to start
2. OR Run yum update from the terminal as root
3. Or Run the Package Manager (Add/Remove Software)
  
Actual results:

See above error messages.


Expected results:

System update completes successfully.

Comment 1 seth vidal 2009-05-04 14:38:46 UTC

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


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