Indeed running as non-root fixes the issue.<div><br></div><div>Thanks for the detailed description.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 16, 2012 at 9:51 AM, Panu Matilainen <span dir="ltr"><<a href="mailto:pmatilai@laiskiainen.org" target="_blank">pmatilai@laiskiainen.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 11/15/2012 04:30 PM, Thomas wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When I run /usr/lib/rpm/rpmdb_stat -CA :<br>
<br>
Default locking region information:<br>
24857 Last allocated locker ID<br>
0x7fffffff Current maximum unused locker ID<br>
5 Number of lock modes<br>
1000 Maximum number of locks possible<br>
1000 Maximum number of lockers possible<br>
1000 Maximum number of lock objects possible<br>
160 Number of lock object partitions<br>
0 Number of current locks<br>
20 Maximum number of locks at any one time<br>
5 Maximum number of locks in any one bucket<br>
0 Maximum number of locks stolen by for an empty partition<br>
0 Maximum number of locks stolen for any one partition<br>
999 Number of current lockers<br>
1000 Maximum number of lockers at any one time<br>
0 Number of current lock objects<br>
5 Maximum number of lock objects at any one time<br>
1 Maximum number of lock objects in any one bucket<br>
0 Maximum number of objects stolen by for an empty partition<br>
0 Maximum number of objects stolen for any one partition<br>
90021 Total number of locks requested<br>
90021 Total number of locks released<br>
0 Total number of locks upgraded<br>
13509 Total number of locks downgraded<br>
18 Lock requests not available due to conflicts, for which we waited<br>
0 Lock requests not available due to conflicts, for which we did not wait<br>
0 Number of deadlocks<br>
0 Lock timeout value<br>
0 Number of locks that have timed out<br>
0 Transaction timeout value<br>
0 Number of transactions that have timed out<br>
752KB The size of the lock region<br>
46 The number of partition locks that required waiting (0%)<br>
20 The maximum number of times any partition lock was waited for (0%)<br>
0 The number of object queue operations that required waiting (0%)<br>
65 The number of locker allocations that required waiting (0%)<br>
0 The number of region locks that required waiting (0%)<br>
1 Maximum hash bucket length<br>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<u></u>=-=-=-=-=-=-=-=-=-=<br>
<br>
It seems the Number of current lockers is the issue.<br>
So the db may no be corrupted but just out of lockers.<br>
</blockquote>
<br></div></div>
Yup, running out of lockers is not corruption, its just out of resources. It does prevent further rpmdb opens unless dealt with though...<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Any idea on why ?<br>
</blockquote>
<br></div>
Well, something is leaving open rpmdb / iterator handles around. To find what that something is, 'fuser -uv /var/lib/rpm/*' should give clues.<br>
<br>
One possibility is something (maybe mash) hitting this: <a href="http://rpm.org/ticket/820" target="_blank">http://rpm.org/ticket/820</a>. While the dangling iterators issue is entirely avoidable with careful programming, older rpm versions (such as the one in RHEL 6) isn't doing a very good job of managing its resources. IIRC yum's API has or at least had some corners where it was all too easy to trigger this issue which arguably is a bug in rpm.<br>
<br>
Like Bill noted, an easy workaround should be running as non-root, as unprivileged rpmdb accesses uses a private "locker room" which is wiped out from existance after use so stale locks from unclosed / dangling iterators dont get to pile up.<div class="HOEnZb">
<div class="h5"><br>
<br>
- Panu -<br>
--<br>
buildsys mailing list<br>
<a href="mailto:buildsys@lists.fedoraproject.org" target="_blank">buildsys@lists.fedoraproject.<u></u>org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/buildsys" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/buildsys</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>
Thomas<br>
</div>