Bug 491035 - yum: rpmdb open failed
Summary: yum: rpmdb open failed
Keywords:
Status: CLOSED DUPLICATE of bug 495087
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 10
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-19 02:27 UTC by Tenshi
Modified: 2014-01-21 23:08 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-04-22 17:44:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tenshi 2009-03-19 02:27:35 UTC
Error Type: <type 'exceptions.TypeError'>
Error Value: rpmdb open failed
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2314, in <module>
    main()
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2310, in main
    backend = PackageKitYumBackend('', lock=True)
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 182, in __init__
    self.yumbase = PackageKitYumBase(self)
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2253, in __init__
    self.repos.confirm_func = self._repo_gpg_confirm
  File : /usr/lib/python2.5/site-packages/yum/__init__.py, line 589, in <lambda>
    repos = property(fget=lambda self: self._getRepos(),
  File : /usr/lib/python2.5/site-packages/yum/__init__.py, line 395, in _getRepos
    self._getConfig() # touch the config class first
  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)

Comment 1 Tim Lauridsen 2009-03-22 08:53:01 UTC
Do you get the same error running

yum update

Comment 2 Tenshi 2009-03-22 18:43:54 UTC
No, this error only happened that day. I have since done updates without a problem. I have not been able to reproduce it. I think is because something did not load right that day. Fedora and other distros need to figure out how to load everything correctly and in order.

Comment 3 Christopher Beland 2009-04-22 17:44:10 UTC
This looks like the same problem as in bug 495087 (which has more detail), so I'm marking this report as a duplicate.  If you happen to remember if there was anything unusual about the *previous* run of yum or PackageKit, that might be useful information to add to the other report.  Likewise if you were using more than one package-related program at the same time.

If you aren't able to dredge up any of that information, thanks anyway for your report; hopefully it will contribute to making yum more robust in the future.

*** 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.