rpm all wacked?

Fred A. Shaul info at zaptech.com
Fri Apr 16 09:22:55 UTC 2004


I see similar discussion of this in an old thread from about a year ago ...
   http://www.uwsg.iu.edu/hypermail/linux/kernel/0304.0/1376.html

Alan Cox no less weighing in on it.  I don't see any resolution though.
  Thoughts?


From: "duncan brown" <duncanbrown at linuxadvocate.net>
> i must ammend my last post: that should NEVER work, you ALWAYS need 
> to rebuild the rpm database > after removing those files.  **those 
> are your rpm database files**
> 
> i think this was a problem introduced as early as redhat 8, if i'm 
> not mistaken  (could be 9, i jumped from 7.3 to 9 on my server, which
>  is the only place i've seen it happen)


Vladimir G. Ivanovic said:
>> Whenever I have RPM problems of any sort (hang, errors) I 
>> immediately delete the __db.00{1,2.3} files (usually) in 
>> /var/lib/rpm:
>> 
>> If that doesn't help, I rebuild the RPM database: rpm --rebuilddb


>>>>>>>>>>>> "fs" == Fred Shaul <info at zaptech.com> writes:
When I try simple rpm commands, and or invoke them using up2date
getting errors ... Help!

# rpm -qa
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
  no packages

# uname -a
Linux bilbo.scalix.local 2.4.22-1.2115.nptl #1
Wed Oct 29 15:42:51 EST 2003 i686
i686 i386 GNU/Linux

# cat /etc/fedora-release
Fedora Core release 1 (Yarrow)







More information about the fedora-list mailing list