From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041020 Description of problem: Version-Release number of selected component (if applicable): rpm-4.4.1 How reproducible: Didn't try Steps to Reproduce: 1. Install fc4test1 2. up2date -u --nosig (do this as text not as gui version) That was it. :( Actual Results: After some time, up2date just sat there... [409] xorg-x11-twm ##### 100% [410] yum ##### 100% ..and sat there. top revealed nothing useful (other than a gdm-binary process munching CPU) strace said futex(0x1460c44, FUTEX_WAIT, 1, NULL <unfinished> gdb said nothing helpful. In the end, I did ^C on it and re-ran up2date. It now thinks that it is up to date and that it needs download nothing more. Despite rpm --rebuilddb though, I seem to have two copies of most rpms on the machine. Additional info: cc'ing because I got told to :) script attached with more useful output.
Created attachment 112711 [details] script with output of ps aux, strace and gdb
Could you attach /var/log/rpmpkgs /root/install.log and the output of rpm --qf '%{name}-%{version}.%}release}.%{arch}\n' -qa
Created attachment 112714 [details] /var/log/rpmpkgs
Created attachment 112715 [details] /root/install.log
Created attachment 112716 [details] The rpm --qf one.
I experienced an rpm hang on u2pdate, when stracing it was sitting on futex as well. This is on: Red Hat Enterprise Linux AS release 3 (Taroon Update 5) more specifically, it was after doing an update -u from update 2 (I believe). I rebooted after up2date -u and rpm -qa would hang, and up2date would hang as well. This was corrected with a reboot, but sounds similar to this problem so I thought I would log a comment in here.
This is likely to be a stale lock and non-reproducible. Display stale locks by doing cd /var/lib/rpm /usr/lib/rpm/rpmdb_stat -CA The normal quiescent (i.e. rpm not running) state is no locks. Fix stale locks by doing rm -f /var/lib/rpm/__db*
Why is this bug reopened without additional information?
This issue was attached to a Red Hat Global support ticket. But you are correct it shouldn't be as this was against FC4-test1.
It also happens to me on: Red Hat Enterprise Linux AS release 3 (Taroon Update 5)