Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 492917

Summary:	deadlock in futex while installing IBM MQ Series v5.3 with RPM
Product:	Red Hat Enterprise Linux 5	Reporter:	Alex Vilensky <alex.vilensky>
Component:	rpm	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED NOTABUG	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.0	CC:	ffesti
Target Milestone:	rc
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-08 12:07:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alex Vilensky 2009-03-30 18:06:17 UTC

Description of problem:

rpm -Uvh command deadlocks in futex while installing IBM MQ Series version 5.3


Version-Release number of selected component (if applicable):

it's a standard version of rpm that comes with distro


How reproducible:

Can send you the rpms upon request.

Steps to Reproduce:
1. rpm -Uvh MQSeriesRuntime-5.3.0-1.i386.rpm - installs normally
2. rpm -Uvh MQSeriesRuntime-U486878-5.3.0-4.i386.rpm - gets stuck in futex
3. Removing __db files and killing rpm has no effect  

Actual results:

deadlock in futex

Expected results:

normal installation

Additional info:
available upon request

Comment 1 Florian Festi 2013-03-08 12:07:56 UTC

This looks like a problem with one of the scriptlets of the package. Most likely it is executing rpm itself which is known to have problems and should be avoided. Please reopen if there are other signs of other origins of the issue.