On Wed, 7 Jan 2009, t35t0r wrote:
On Wed, Jan 7, 2009 at 10:23 AM, Gabriel Craciun <[email protected]> wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=453037
yeah, I hope a patched version of yum is released soon, I don't want
to have to --rebuilddb every 20 days.
This is NOT database corruption, it's just running out of locks.
As for the reason, there are basically two possibilities:
a) Process crashing while holding an rpmdb lock. Prior to the updated
rpm in RHEL 5.3, a python process tracebacking while holding a lock
on rpmdb would always leave a stale lock behind, the rpm version
in 5.3 takes care of cleaning up locks on unclean exit from python.
b) A long-lived process acquiring locks and never releasing them.
Bug #453037 on yum-updatesd falls into this category, ie should
be fixed in errata.
To find out what's holding the locks, this will tell you:
# fuser -av /var/lib/rpm/__db.001
Gently terminating the process(es) holding those locks should clean up the
situation, if not then *after* killing all processes holding the locks do
"rm -f /var/lib/rpm/__db*" to clear the environment which contains the
locks and you're done. rpm --rebuilddb is NOT necessary here.
- Panu -
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
