[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: yum update: Fatal error, run database recovery ??



On 04/18/2009 03:42 AM, Jerry Amundson wrote:
> On Fri, Apr 17, 2009 at 3:16 PM, sean darcy <seandarcy2 gmail com> wrote:
>> On F11 beta:
>>
>> yum update
>> Loaded plugins: fastestmirror, refresh-packagekit
>> rpmdb: Thread/process 3935/140267357374192 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
>> Traceback (most recent call last):
>>  File "/usr/bin/yum", line 29, in <module>
>>    yummain.user_main(sys.argv[1:], exit_code=True)
>>  File "/usr/share/yum-cli/yummain.py", line 309, in user_main
>>    errcode = main(args)
>>  File "/usr/share/yum-cli/yummain.py", line 157, in main
>>    base.getOptionsConfig(args)
>>  File "/usr/share/yum-cli/cli.py", line 187, in getOptionsConfig
>>    self.conf
>>  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 239, in
>> _getConfig
>>    self._conf = config.readMainConfig(startupconf)
>>  File "/usr/lib/python2.6/site-packages/yum/config.py", line 794, in
>> readMainConfig
>>    yumvars['releasever'] = _getsysver(startupconf.installroot,
>> startupconf.distroverpkg)
>>  File "/usr/lib/python2.6/site-packages/yum/config.py", line 867, in
>> _getsysver
>>    idx = ts.dbMatch('provides', distroverpkg)
>> TypeError: rpmdb open failed
>>
>> And this didn't fix it:
>> rpm --rebuilddb
>> rpmdb: Thread/process 3935/140267357374192 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)
>>
>> I'll file a bug, but how can I fix this in the meantime?
> 
> Reboot? Odd, I know, but I've had to on occasions where updates put
> libraries in confused states.

It might also work because /etc/rc.sysinit has

"rm -f /var/lib/rpm/__db* &> /dev/null"

Rahul


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]