Bug 450705

Summary: yum deadlock
Product: [Fedora] Fedora Reporter: Bill C. Riemers <briemers>
Component: rpmAssignee: Panu Matilainen <pmatilai>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: ffesti, james.antill, jnovy, katzj, pmatilai, pnasrat, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-31 09:36:42 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:
Attachments:
Description Flags
Output of strace -o yum.log -f yum update none

Description Bill C. Riemers 2008-06-10 15:27:06 UTC 
Description of problem:

Yum is deadlocking in "Setting up Update process".

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

yum-metadata-parser-1.1.2-8.fc9.x86_64
yum-packagekit-0.2.2-2.20080529.fc10.x86_64
yum-utils-1.1.13-2.fc9.noarch
yum-3.2.16-2.fc9.noarch

How reproducible:

100% on my system.

Steps to Reproduce:
1. run yum update
2.
3.
  
Actual results:

deadlocks

Expected results:

install updates

Additional info:

I see I am not the only person with this trouble:

http://www.linuxquestions.org/questions/fedora-35/fc9-yum-freezes
Comment 1 Bill C. Riemers 2008-06-10 15:30:03 UTC 
Created attachment 308825 [details]
Output of strace -o yum.log -f yum update

I have to use kill -9 to terminate this process.
Comment 2 James Antill 2008-06-10 15:50:53 UTC 
 The last part of the strace is:

20191 open("/var/lib/rpm/Packages", O_RDONLY) = 9
20191 fcntl(9, F_SETFD, FD_CLOEXEC)     = 0
20191 fstat(9, {st_mode=S_IFREG|0644, st_size=57294848, ...}) = 0
20191 rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
20191 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
20191 pread(9,
"\0\0\0\0\1\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\340\0\227\10\0\2\373\17\366\17\361\17"...,
4096, 4096) = 4096
[...]
20191 pread(9,
"\0\0\0\0\1\0\0\0\271/\0\0\270/\0\0\0\0\0\0\1\0\302\2\0\7doc/\0/"..., 4096,
50040832) = 4096
20191 futex(0x7f4af5d3b2f8, FUTEX_WAIT, 2, NULL) = ? ERESTARTSYS (To be restarted)
Comment 3 James Antill 2008-06-10 15:53:34 UTC 
 If you are sure nothing else is using rpm, you can probably fix this by doing:

   rm -f /var/lib/rpm/__db*
Comment 4 seth vidal 2008-06-10 16:03:56 UTC 
and then you probably want to run: rpm --rebuilddb
Comment 5 Christopher Beland 2008-10-23 01:53:18 UTC 
This looks like it might be the same problem as in bug 444321.
Comment 6 Panu Matilainen 2009-01-31 09:36:42 UTC 

*** This bug has been marked as a duplicate of bug 444321 ***