Description of problem: I was running debuginfo-install and it took so long that I have to SIGKILL it, now, when I run yum upgrade, it fails like this: newman abrt-root $ sudo yum upgrade rpmdb: Thread/process 25047/3087275712 failed: Thread died in Berkeley DB library error: db4 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm /usr/lib/python2.6/site-packages/yum/config.py:894: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 raise Errors.YumBaseError("Error: " + e.message) CRITICAL:yum.main: Error: rpmdb open failed newman abrt-root $ ps axu | grep rpm newman 25126 0.0 0.0 4244 736 pts/0 S+ 10:51 0:00 grep --color=auto rpm newman abrt-root $ ps axu | grep yum newman 25128 0.0 0.0 4244 736 pts/0 S+ 10:51 0:00 grep --color=auto yum newman abrt-root $ cat /var/loc local/ lock/ newman abrt-root $ cat /var/lock/yum* cat: /var/lock/yum*: No such file or directory Looks like the rpmdb is broken somehow, but can the output from yum be enhanced a bit? Removing the code making DeprecationWarning and having the CRITICAL msg a bit shaped would be nice. Version-Release number of selected component (if applicable): yum-3.2.24-3.fc12.noarch rpm-4.7.1-4.fc12.i686 yum-utils-1.1.23-3.fc12.noarch
there are multiple things going on here. normally yum would exit with: Critical: yum.main: Error: rpmdb open failed however b/c of a change in python there is a deprecation warning that is being emitted and, I guess, that's what is triggering abrt?
Nothing triggered abrt, I was just in abrt's local root dir at that time :). So, I guess I'd be glad than if yum got rid of the deprecation warning.
done upstream http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=705ae2132f469037b9a77459aeab18a23fc08dd1
Both are now fixed upstream.