Description of problem: error when trying to install fedora-gpg-key
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. su --login
2. rpm --import http://macromedia.mplug.org/FEDORA-GPG-KEY
" warning: cannot get exclusive lock on /var/lib/rpm/Packages "
ehh, doing the job? It had worked many other times.
Fresh install F7, full updated, I am following
http://www.fedorasolved.org/browser-solutions/flash/ this howto has always work.
[crash@localhost ~]$ su -c 'yum -y update'
Loading "installonlyn" plugin
Setting up Update Process
No Packages marked for Update/Obsoletion
[crash@localhost ~]$ su --login
[root@localhost ~]# rpm --import http://macromedia.mplug.org/FEDORA-GPG-KEY
warning: cannot get exclusive lock on /var/lib/rpm/Packages
This probably means that some other process such as yum-updatesd or rpmq
currently has a lock on the database. Try again later. Someone I was helping
got the same warning during a rpm --import command, but it worked later.
Tried several times, for around 6h, no luck, it worked flawlessly after a reboot
If it actually requires a reboot, then the lock isn't getting released after
the other process is finished, which _would_ be a bug. I don't remember whether
the person I was helping rebooted between the time it failed and when it
succeeded, but it's possible.
Yep. Contention for an rpmdb lock is orders of magnitude worse
now that yum has *several* competing daemons.
rm -f /var/lib/rpm/__db*
and attempting the --import before the next acquisition of the rpmdb lock
by yum-updatesd is recommended.
Sounds like a possible side-effect of bug 245389, which in short appears to be
setroubleshoot tracebacking a lot for some people and causing stale rpmdb locks
to be left behind. The rpm package from updates-testing should help, if not 100%
fix the problem.
*** This bug has been marked as a duplicate of 246564 ***