Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionDavid Zambonini
2016-01-06 15:43:59 UTC
Created attachment 1112210[details]
rpm db4 messages should go to stderr
Description of problem:
Some rpm pre/post scripts rely on a shell out to rpm to determine pre-existing installed package information/versioning. (e.g. `rpm -q --provides mysql-server 2> /dev/null`)
Unfortunately some non-fatal warnings can be output if, for example, a read lock on the rpmdb is held open at this time, leading to the warning picked up as the output and causing breakage:
Freeing read locks for locker 0x49e: 482061/47810768245328
mysql-server-5.1.73-5.el6_6.x86_64
(both lines on stdout)
Putting aside the question of what is holding the read lock open for a second, this behaviour is obviously erroneous -- warnings/errors should be output to stderr, not stdout.
How reproducible:
`rpm -q --provides mysql-server 2> /dev/null`
While read lock held open on rpmdb. Cannot provide a reproducer for this as unfortunately is enivornment dependent.
Actual results:
Freeing read locks for locker 0x49e: 482061/47810768245328
mysql-server-5.1.73-5.el6_6.x86_64
Expected results:
Freeing read locks for locker 0x49e: 482061/47810768245328 (on stderr)
mysql-server-5.1.73-5.el6_6.x86_64 (on stdout)
Additional info:
The behaviour is caused by db4, which if no msgfile is specified, defaults to stdout. There is a simple fix, however, which without modifying default db4 behaviour that merely involves rpm passing stderr as the msgfile at initialisation (patch supplied).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-0936.html
Created attachment 1112210 [details] rpm db4 messages should go to stderr Description of problem: Some rpm pre/post scripts rely on a shell out to rpm to determine pre-existing installed package information/versioning. (e.g. `rpm -q --provides mysql-server 2> /dev/null`) Unfortunately some non-fatal warnings can be output if, for example, a read lock on the rpmdb is held open at this time, leading to the warning picked up as the output and causing breakage: Freeing read locks for locker 0x49e: 482061/47810768245328 mysql-server-5.1.73-5.el6_6.x86_64 (both lines on stdout) Putting aside the question of what is holding the read lock open for a second, this behaviour is obviously erroneous -- warnings/errors should be output to stderr, not stdout. How reproducible: `rpm -q --provides mysql-server 2> /dev/null` While read lock held open on rpmdb. Cannot provide a reproducer for this as unfortunately is enivornment dependent. Actual results: Freeing read locks for locker 0x49e: 482061/47810768245328 mysql-server-5.1.73-5.el6_6.x86_64 Expected results: Freeing read locks for locker 0x49e: 482061/47810768245328 (on stderr) mysql-server-5.1.73-5.el6_6.x86_64 (on stdout) Additional info: The behaviour is caused by db4, which if no msgfile is specified, defaults to stdout. There is a simple fix, however, which without modifying default db4 behaviour that merely involves rpm passing stderr as the msgfile at initialisation (patch supplied).