While using the apt-get command or the relatively new APT package management tool in Ubuntu Linux or its derivatives such as Linux Mint (which I actually use as my primary operating system for doing daily work), you might have encountered the error – “unable to lock the administration directory (/var/lib/dpkg/) is another process using it” on the command line.
This error can be so annoying especially for new Linux (Ubuntu) users who may not know exactly the cause of the error.
Below is an example, showing the lock file error in Ubuntu 16.10:
[email protected]:~$ sudo apt install neofetch [sudo] password for tecmint: E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable) E: Unable to lock the administration directory (/var/lib/dpkg), is another process using it?
The output below is another possible instance of the same error:
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable) E: Unable to lock directory /var/lib/apt/lists/ E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable) E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
How can you solve the above error in case you bump into it in the future? There are several ways of dealing with this error(s), but in this guide, we will go through the two easiest and probably the most effective ways of solving it.
1. Find and Kill all apt-get or apt Processes
Run the command below to generate a list of all processes whose name comprises of the word apt, you will get a list inclusive of all apt or apt-get processes by using ps
and grep commands together with a pipeline.
$ ps -A | grep apt

For each apt-get or apt process that you can see in the output of the command above, kill each process using the command below.
The process ID (PID) is found in the first column from the screenshot above.
$ sudo kill -9 processnumber OR $ sudo kill -SIGKILL processnumber
For instance, in the command below where 9
is the signal number for the SIGKILL signal, will kill the first apt process:
$ sudo kill -9 13431 OR $ sudo kill -SIGKILL 13431
2. Delete the lock Files
A lock file simply prevents access to another file(s) or some data on your Linux system, this concept is present in Windows and other operating systems as well.
Once you run an apt-get or apt command, a lock file is created under the any of these directories /var/lib/apt/lists/, /var/lib/dpkg/ and /var/cache/apt/archives/.
This helps to avoid the apt-get or apt process that is already running from being interrupted by either a user or other system processes that would need to work with files being used by apt-get or apt. When the process has finished executing, the lock file is then deleted.
Important: In case a lock is still exiting in the two directories above with no noticeable apt-get or apt process running, this may mean the process was held for one reason or the other, therefore you need to delete the lock files in order to clear the error.
First execute the command below to remove the lock file in the /var/lib/dpkg/
directory:
$ sudo rm /var/lib/dpkg/lock
Afterwards force package(s) to reconfigure like so:
$ sudo dpkg --configure -a
Alternatively, delete the lock files in the /var/lib/apt/lists/
and cache directory as below:
$ sudo rm /var/lib/apt/lists/lock $ sudo rm /var/cache/apt/archives/lock
Next, update your packages sources list as follows:
$ sudo apt update OR $ sudo apt-get update
In conclusion, we have walked through two important methods to deal with a common problem faced by Ubuntu (and its derivatives) users, while running apt-get or apt as well as aptitude commands.
Do you have any other reliable methods to share meant for deal with this common error? Then get in touch with us via the feedback form below.
In addition, you may as well want to learn how to find and kill running processes and read through a simple guide to kill, pkill and killall commands to terminate a process in Linux.
Dear Aaron,
Thanks for your response, it helped me a lot, in my situation I am new to linux. It is a powerful technology for those who know how to use it.
=)
@Pablo
Welcome and thanks for the feedback.
HI, i followed this procedure yesterday and it worked, but i am fcing the same problem today too. will i have to be doing this everyday, or there is a way i can stop it once and for all
@Olivia
This should not happen everyday, but in case it continues to happen, use the provided solutions.
Thank you so much. it is very easy to follow and understand
@Olivia
Welcome, many thanks for the feedback.
This article is so simple and easy to understand. Saved my day! Thanks Aaron!
@Sneha
Welcome, thanks a lot for the feedback.
Thank you so much Aaron Kili. You saved me. Thanks a lot.
@Valli
Welcome, thanks for the feedback.
Hi,
I am trying for a long time to install Kali Linux from MS store but failed always, after running “sudo sh.xfce4.sh” command.
When I run “sudo/etc/init.d/xrdp start” it says” No such file or directory not found”
Kindly guide
I am getting these errors..
Err:1 http://in.archive.ubuntu.com/ubuntu artful InRelease
Could not resolve 'in.archive.ubuntu.com'
Err:2 http://in.archive.ubuntu.com/ubuntu artful-updates InRelease
Could not resolve 'in.archive.ubuntu.com'
Err:3 http://in.archive.ubuntu.com/ubuntu artful-backports InRelease
Could not resolve 'in.archive.ubuntu.com'
Err:4 http://archive.canonical.com/ubuntu artful InRelease
Could not resolve 'archive.canonical.com'
Err:5 http://security.ubuntu.com/ubuntu artful-security InRelease
Could not resolve 'security.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/artful/InRelease Could not resolve 'in.archive.ubuntu.com'
W: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/artful-updates/InRelease Could not resolve 'in.archive.ubuntu.com'
W: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/artful-backports/InRelease Could not resolve 'in.archive.ubuntu.com'
W: Failed to fetch http://archive.canonical.com/ubuntu/dists/artful/InRelease Could not resolve 'archive.canonical.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/artful-security/InRelease Could not resolve 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
@Ganesh
Ensure that your device is connected to the internet. You can test using ping, try to ping google.com or any popular servers.
Hi Sir,
it is coming like this after typing given commands.
@srujan
What commands in particular, just be a little clear on the question so we can help you easily. Hope you have understood.
thanks brother, its working! I recently bought a vps and it had the same issue but now its fixed. Thank you :)
@Manal
Welcome, we are glad that you found this guide helpful. Thanks for the feedback.
thanks aaron
@lucky
We are lucky to have you following us, thanks for the feedback.