Hi, everyone, I am running F10. I attempted to review some yum groups using the Add/Remove Software button, and the window gives me the following error:
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)
If I am reading this debug message correctly, it appears that a lock file is in place. But the path is not given.
If I use a terminal and do yum commands directly (I tried several, but didn't keep a log) they seem to work correctly. So this appears to be some lock that is generated by the Add/Remove Software utility, and not yum itself.
Any clues? Looking up the yum help on line didn't provide any illumination (as I expected, since this appears to be the window, and not the utility).
Regards, Les H
Les wrote:
If I am reading this debug message correctly, it appears that a lock file is in place. But the path is not given.
There are numbered files matching the pattern: /var/lib/rpm/__db.???
These are used to access the actual RPM database and also hold its locks. Deleting these files allows recovering from locking issues.
WARNING: Do not delete any other files in /var/lib/rpm!
Kevin Kofler
On Wed, 2009-03-18 at 21:23 +0100, Kevin Kofler wrote:
Les wrote:
If I am reading this debug message correctly, it appears that a lock file is in place. But the path is not given.
There are numbered files matching the pattern: /var/lib/rpm/__db.???
These are used to access the actual RPM database and also hold its locks. Deleting these files allows recovering from locking issues.
WARNING: Do not delete any other files in /var/lib/rpm!
Kevin Kofler
It turned out that I had to reboot (power issues), and during that exercise, the locks cleared, and yum is back to working again.
But thanks for the reminder about the database files. I should have thought of that.
Regards, Les H