Bug 430108

Created attachment 292802 [details]
Dump File

I was able to get the software update to run by doing the following:
cd /var/lib/rpm
rm *db.00*

then I was able to run the software updater.
rhn.redhat.com/rhn/systems  reports this server as pending actions required.

uname -r still reports the kernel as 2.6.18-53.el5
and the system still thinks that there is an update to install

I have the same problem: all the packet managing programs give the log I'm going to attach. I'm stuck.
I think this is a clone, but I don't know how to merge it with this one; it's also very old:

https://bugzilla.redhat.com/show_bug.cgi?id=219579

I forgot: I have Fedora 10. I don't know which versions I have to look for, I have:

yum-3.2.21-2.fc10.noarch

Another detail: I was looking for a packet in the "Add/Remove software" window when I stopped the search and a message box appeared saying that all the packages weren't modified. Who asked it? I don't know. The bug started there.

What, this thread is open since a year ago? And on a RHEL distro? I hope someone answers me, otherwise... I hope!

Created attachment 333616 [details]
The log of all the programs

I know how to reproduce the issue, but it's a gnome-packagekit one, yum's got nothing to do with that in my case. This is the new bug trace:

https://bugzilla.redhat.com/show_bug.cgi?id=487924

when trying to add software from repository in fedora 10:

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)

When trying to update system:

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)

When refresh button is clicked: ( same result shown in comment #9 )

This means the rpmdb is locked by something else ... but we can't reproduce this. Can someone run:

# cd /var/lib/rpm
# /usr/lib/rpm/rpmdb_stat -c

...as I've seen bugs where rpm runs out of locks.

I forgot to say that my issue is different, I've posted my bug here:

https://bugzilla.redhat.com/show_bug.cgi?id=487924

and when I reboot the system I can use the various package managers.
Sorry for being grumpy, but I was worried when I couldn't install a program I was needing...!

(In reply to comment #12)
> This means the rpmdb is locked by something else ... but we can't reproduce
> this. Can someone run:
> 
> # cd /var/lib/rpm
> # /usr/lib/rpm/rpmdb_stat -c

Sure:

# /usr/lib/rpm/rpmdb_stat -c
31	Last allocated locker ID
0x7fffffff	Current maximum unused locker ID
5	Number of lock modes
1000	Maximum number of locks possible
1000	Maximum number of lockers possible
1000	Maximum number of lock objects possible
3	Number of current locks
4	Maximum number of locks at any one time
3	Number of current lockers
4	Maximum number of lockers at any one time
3	Number of current lock objects
4	Maximum number of lock objects at any one time
2156	Total number of locks requested
2152	Total number of locks released
0	Total number of locks upgraded
22	Total number of locks downgraded
0	Lock requests not available due to conflicts, for which we waited
0	Lock requests not available due to conflicts, for which we did not wait
0	Number of deadlocks
0	Lock timeout value
0	Number of locks that have timed out
0	Transaction timeout value
0	Number of transactions that have timed out
344KB	The size of the lock region
0	The number of region locks that required waiting (0%)

*** Bug 498328 has been marked as a duplicate of this bug. ***

Error Type: <class 'yum.Errors.ConfigError'>
Error Value: Error accessing file for config file:///etc/yum.conf
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2828, in <module>
    main()
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2824, in main
    backend = PackageKitYumBackend('', lock=True)
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 196, in __init__
    self.yumbase = PackageKitYumBase(self)
  File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2767, in __init__
    self.repos.confirm_func = self._repo_gpg_confirm
  File : /usr/lib/python2.6/site-packages/yum/__init__.py, line 643, in <lambda>
    repos = property(fget=lambda self: self._getRepos(),
  File : /usr/lib/python2.6/site-packages/yum/__init__.py, line 448, in _getRepos
    self.conf # touch the config class first
  File : /usr/lib/python2.6/site-packages/yum/__init__.py, line 649, in <lambda>
    conf = property(fget=lambda self: self._getConfig(),
  File : /usr/lib/python2.6/site-packages/yum/__init__.py, line 217, in _getConfig
    startupconf = config.readStartupConfig(fn, root)
  File : /usr/lib/python2.6/site-packages/yum/config.py, line 763, in readStartupConfig
    confpp_obj = ConfigPreProcessor(configfile)
  File : /usr/lib/python2.6/site-packages/yum/parser.py, line 86, in __init__
    fo = self._pushfile( url )
  File : /usr/lib/python2.6/site-packages/yum/parser.py, line 195, in _pushfile
    'Error accessing file for config $s' $ (absurl)

I HAVE NO IDEA FOR WHAT THIS IS, IT COMES EVERYTIME I TRY TO USE THE ADD/REMOVE SOFTWARE TOOL ON THE ADMINISTRATOR IN FEDORA 10

Ignoring all the Fedora related comments which dont belong to this bug at all...

Rebasing rpm to a newer Berkeley DB version which would allow automatic stale lock cleanup is not something we can do in RHEL-5, manually clearing the environment is required if it gets stuck eg due to running out of locks. In RHEL-6 stale locks are automatically cleaned so rpmdb open failures are rarer. Also yum shouldn't expect rpmdb open always succeeds, but IIRC this too is fixed in newer versions.