Bug 97002 - all rpm/up2date actions stalled
Summary: all rpm/up2date actions stalled
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm
Version: 9
Hardware: i686
OS: Linux
high
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-08 14:42 UTC by Christopher Chan
Modified: 2007-03-27 04:06 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-06-10 18:59:40 UTC
Embargoed:


Attachments (Terms of Use)

Description Christopher Chan 2003-06-08 14:42:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.3a) Gecko/20021207
Phoenix/0.5

Description of problem:
Any actions (install,query, upgrade) related to rpm/up2date will become stalled.

rpm -qa, rpm -ivh package, rpm -Uvh package

They used to work VERY slowly...and now not at all

strace -p pid of all stalled/slow rpm commands show them in the following state:

strace -p 26429
futex(0x4060074c, FUTEX_WAIT, 0, NULL


Version-Release number of selected component (if applicable):
the rpm package that comes with RH9

How reproducible:
Always

Steps to Reproduce:
1. run rpm (any action, query, install, upgrade)
2. it will stall
3. strace -p
    

Actual Results:  found rpm in futex(0xXXXXXX, FUTEX_WAIT, 0, NULL

Expected Results:  the action requested to execute properly

Additional info:

Comment 1 Christopher Chan 2003-06-10 05:55:00 UTC
Please help out with this, not being able to up2date or use rpm to upgrade
updated packages that were downloaded ain't fun.

Comment 2 Jeff Johnson 2003-06-10 15:05:10 UTC
Try
    rm -f /var/lib/rpm/__db*
to remove stale locks.

Does that fix?

Missed SIGPIPE is usual cause of stale locks.
That's fixed in rpm-4.2-1 (for Red Hat 9) and
rpm-4.1.1 (for Red Hat 8.0) packages at
    ftp://ftp.rpm.org/pub/rpm/dist

Comment 3 Christopher Chan 2003-06-10 15:58:12 UTC
ah, yes that helped. up2date is now underway. thnx.


Note You need to log in before you can comment on or make changes to this bug.