Console problems, RPM cannot create due to transaction lock???
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Console problems, RPM cannot create due to transaction lock???
Ok
I've downloaded some software to install onto my system.
I open up my console and type in:
rpm -i productname.rpm
Now I receive the error message:
error: cam't create transaction lock on /var/lib/rpm/__db.000
I check my man on transaction lock, and notices it says a Lock on a table?? why is it referring to a database table lock? Then I notice further in my read that there is no unlock table command.
Can a guru gimme a heads up on what needs to be performed in order to install my rpm package??? without having the error of a transaction lock.
First, make sure you are installing this as root, as users don't have read/write permissions on the rpm database by default. Second, if root gets the same error, make sure you don't have another package manager running somewhere (urpmi, yast, etc).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.