"rpm --rebuilddb" fails to error.

Tommi · 04-18-2003, 08:08 AM

Yo!

I usually use

$ rpm --rebuilddb

after installation. It seems good idea to rebuild rpm database after installation...am I right?

Anyway it fails because device or resource is busy.

How to find out what is this device or resource which is busy and how to disable it so I can rebuild my database?

Thanks for help.

-Tommi

cnjohnson · 04-18-2003, 11:15 AM

I usually delete the index/lock files in /var/lib/rpm

#rm __db*

These are the files with the leading double underscore. Then, I do the rebuild.

Cheers--
Charles

jessepangburn · 05-04-2003, 12:36 AM

you need to delete those locks, but when you try to rebuild and the locks are the problem- the error message is different- I forget what. In this case, a process already has the rpm database open so you need to kill that process first. I use redhat 9 and there you can use the "System Monitor" to find any rpm processes and kill them. Also look for 'redhat-config-packages' process. Once you kill those, follow cnjohnson's suggestion to delete the lock files, then try the rebuild again.

jessepangburn · 05-04-2003, 12:40 AM

oh, and I suggest using
#rpm --rebuilddb -vv
this gives very verbose output, but since this rebuild can take a long time, it's nice to see because you know it's not just hung up.