RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
noticed warnings regarding freeing read locks

Version-Release number of selected component (if applicable):
rhn-setup-gnome-1.0.0-20.el6.noarch
rhn-setup-1.0.0-20.el6.noarch


How reproducible:
sometime, during package profile gathering, sending

Steps to Reproduce:
1. rhn_register
2. warning messages
  
Actual results:
[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


Expected results:
no warnings

Additional info:

registered on s390x, x86_64

I'm pretty sure those messages come from db4, though I cannot really
reproduce it.

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. 

Cliff

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.