[Yum] Yum (or rpm) no workie with kernel-2.6?

nathan r. hruby nhruby at uga.edu
Sat Nov 29 16:27:14 UTC 2003


Ok, An edge case I know, but... 

So the other day I got crafty and decided to try out Arjan van de Ven's
2.6 test-kernels on a fully patched Red Hat 9 box (Hey, they're yum-ified,
I couldn't resist!).  These kernel's and changelog can be found at:  
http://people.redhat.com/arjanv/2.5/

It appears that these kernels perhaps break either yum, db3/4, rpm, or some
combination thereof - I'm not really sure which.  Here's the error I get
(adding -d 10 to the yum command doesn't reveal anything else):

--- SNIP
tester.foo# yum --version
2.0.3
tester.foo# yum list updates
rpmdb: unable to join the environment
error: db4 error(11) from dbenv->open: Resource temporarily unavailable
error: cannot open Packages index using db3 - Resource temporarily 
unavailable (11)
error: cannot open Packages database in /var/lib/rpm
Traceback (most recent call last):
  File "/usr/bin/yum", line 60, in ?
    yummain.main(sys.argv[1:])
  File "yummain.py", line 118, in main
  File "yummain.py", line 70, in parseCmdArgs
  File "config.py", line 123, in __init__
  File "config.py", line 246, in _getsysver
TypeError: rpmdb open failed
tester.foo# uname -a Linux tester.foo.uga.edu 2.6.0-0.test10.1.98 #1 Wed Nov 26 09:14:46 EST 2003 i686 i686 i386 GNU/Linux
tester.foo# rpm -qi yum
rpmdb: unable to join the environment
error: db4 error(11) from dbenv->open: Resource temporarily unavailable
error: cannot open Packages index using db3 - Resource temporarily unavailable (11)
error: cannot open Packages database in /var/lib/rpm
package yum is not installed
--- END

Any one have an idea?  My initial thought is that this kernel has the
exec-shield patch and that's what's probably causing the ish with db4..  
I've already removed the __db* files from /var/lib/rpm and tried a
--rebuilddb with the same error.

I'm going to reboot back into the old kernel when I get back to the 
machine and try yum again, but seeing as I installed the kernel with yum 
and then rebooted and that's been the only change the kernel looks 
suspect :)  If anyone else has seen similar things or might have a clue to 
share to point me in the right direction before emailing Arjan I'd be 
thankful.

Hope everyone had some good pumpkin pie this week!

-n
-- 
-------------------------------------------
nathan hruby <nhruby at uga.edu>
uga enterprise information technology services
production systems support
metaphysically wrinkle-free
-------------------------------------------



More information about the Yum mailing list