Red Hat Bugzilla – Bug 590675
Lock yum for non-root users, so multiple simultaneous runs don't interact badly
Last modified: 2014-01-21 01:17:33 EST
abrt 1.1.0 detected a crash.
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/yumdownloader --disablerepo=* --enablerepo=*-debug* --quiet keyutils-debuginfo-1.4-1.el6.x86_64
reason: yumRepo.py:1053:_revertOldRepoXML:OSError: [Errno 2] No such file or directory
release: Red Hat Enterprise Linux release 6.0 Beta (Santiago)
How to reproduce
1. Just downloading today's update
Created attachment 412833 [details]
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
You were running this as a normal user?
Was anything else happening at the time?
If it's the problem I think it is (non-root users need some kind of lock), we can probably do it for 6.1
Yeh, the easiest way to test involves keeping old metadata around for a repo.
You can just test that the new yum has locking, but opening two terminals and running "yum search yum" in both of them ... if one of them doesn't start printing the "yum is locked" data, then there is no lock.
> You can just test that the new yum has locking...
Thats the way I have tested bug 669746. But the traceback is a bit different, therefore I am also trying to reproduce the one in #c0. I will try it again with the old metadata.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Cause: yum only had a lock for root, in /var/run
Consequence: you could two instances of yum at once as non-root
Fix: yum now also locks the cache.
Result: You can run two instances, but the second will wait for the lock
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.