yum update: Fatal error, run database recovery ??

Seth Vidal skvidal at fedoraproject.org
Tue Apr 21 15:39:23 UTC 2009



On Tue, 21 Apr 2009, Panu Matilainen wrote:

> Or actually more to the point: sending SIGINT or SIGTERM is fine, rpm blocks 
> that when the db is open. But sending a SIGKILL (like PK does if the backend 
> doesn't terminate quickly) is just Russian roulette - sometimes you get away 
> with it, sometimes you dont.
>
> If SIGKILL happens while rpm is running inside db4 code, with current rpm + 
> db4 combination you'll get one of these:
>
> rpmdb: Thread/process 16507/3086059200 failed: Thread died in Berkeley DB
> library
> error: db4 error(-30975) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, 
> run database recovery
>

Has this been filed, then?

-sv




More information about the fedora-test-list mailing list