Short Tip: Work around rpm lockups

Under certain circumstances it might happen that rpm,a nd therefore yum, doesn’t continue to work. The program will simply not continue any action and also cannot be interrupted any more.
If you strace the problem you will see a string like FUTEX_WAIT.

This is a complicated bug known for years and it will hopefully be fixed at some time in the future. However, until then the best workaround is to quit all running yum/rpm instances and delete some files:

# rm /var/lib/rpm/__db*

A reboot might also help, but this is definitely much faster.


One thought on “Short Tip: Work around rpm lockups”

  1. This is not really a single unfixed bug. The issue is more complicated than that. However the rawhide version of RPM seems to have resolved this issue

    “#Automatic cleaning up of stale rpmdb locks on Berkeley DB >= 4.5.20”

Comments are closed.