Description of problem:
noticed warnings regarding freeing read locks
Version-Release number of selected component (if applicable):
sometime, during package profile gathering, sending
Steps to Reproduce:
2. warning messages
[root@ibm-z10-09 rhn]# rhn_register
Freeing read locks for locker 0x15: 1816/2199028151216
Freeing read locks for locker 0x17: 1816/2199028151216
Freeing read locks for locker 0x18: 1816/2199028151216
registered on s390x, x86_64
I'm pretty sure those messages come from db4, though I cannot really
Panu, do you have any idea what scenario might cause this error to
be propagated from db4 into rpm / rpm-python?
That's just db4's way of saying "previous user of rpmdb made a mess and left stale locks behind, hold your nose while I clean it up".
The message itself is not at all an error, but it does indicate a problem somewhere: some program using rpmdb either crashed or got forcibly killed, or is not freeing up rpmdb-related resources after use.
minor - punting to rhel 6.1, blockers/exceptions only now.
Milan close not a bug if needed (which I think we may) - or look at ways to sanely capture and report/log the messages.
Based on comment #3, I'm closing this with WONTFIX -- there's no way
for us to fix this warning in rhn-client-tools.
Well, if such warnings are regularly seen as part of normal operation, there's a bug somewhere that needs fixing - normal operation must not either forcibly kill rpm-related processes or exit without cleaning up, causing warnings. Whether they're caused by something in rhn-client-tools or somewhere else should be investigated.