Fix “Unable to lock the administration directory (/var/lib/dpkg/)” in Ubuntu

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:

tecmint@TecMint:~$ 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
Find apt and apt-get Processes
Find apt and apt-get Processes

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.

Aaron Kili
Aaron Kili is a Linux and F.O.S.S enthusiast, an upcoming Linux SysAdmin, web developer, and currently a content creator for TecMint who loves working with computers and strongly believes in sharing knowledge.

Each tutorial at TecMint is created by a team of experienced Linux system administrators so that it meets our high-quality standards.

Join the TecMint Weekly Newsletter (More Than 156,129 Linux Enthusiasts Have Subscribed)
Was this article helpful? Please add a comment or buy me a coffee to show your appreciation.

101 thoughts on “Fix “Unable to lock the administration directory (/var/lib/dpkg/)” in Ubuntu”

  1. In the parrot os terminal whenever I try to update using sudo apt-get update it shows a lot of errors I don’t know what to do a lot of Ign:1, and Ign:2 coming up again, and again can you help me how to solve the problem?

    Reply
  2. Is there any biggest problem because of the “unable to lock the administration directory (/var/lib/dpkg/” of this error in the system?

    Reply
  3. Cool is working for me, here is short story

    root@pc-02:/home/user1# apt-get remove && apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    0 upgraded, 0 newly installed, 0 to remove and 767 not upgraded.
    Reading package lists… Done
    E: Could not get lock /var/lib/apt/lists/lock – open (11: Resource temporarily unavailable)
    E: Unable to lock directory /var/lib/apt/lists/

    $ sudo rm /var/lib/dpkg/lock

    Afterward force package(s) to reconfigure like so:

    $ sudo dpkg --configure -a

    $ sudo apt-get remove && apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y

    :) all best

    Reply
  4. Great post, thanks!

    Ran into issue

    fatal: [192.168.56.xxx]: FAILED! => {“changed”: false, “msg”: “‘/usr/bin/aptitude safe-upgrade’ failed: E: Could not open lock file /var/lib/dpkg/lock – open (13: Permission denied)\nE: Unable to lock the administration directory (/var/lib/dpkg/), are you root?\n”, “rc”: 255, “stdout”: “Reading package lists…\nBuilding dependency tree…\nReading state information…\nInitializing package states…\n”, “stdout_lines”: [“Reading package lists…”, “Building dependency tree…”, “Reading state information…”, “Initializing package states…”]}

    fatal: [192.168.56.xxx]: FAILED! => {“changed”: false, “msg”: “‘/usr/bin/aptitude safe-upgrade’ failed: E: Could not open lock file /var/lib/dpkg/lock – open (13: Permission denied)\nE: Unable to lock the administration directory (/var/lib/dpkg/), are you root?\n”, “rc”: 255, “stdout”: “Reading package lists…\nBuilding dependency tree…\nReading state information…\nInitializing package states…\n”, “stdout_lines”: [“Reading package lists…”, “Building dependency tree…”, “Reading state information…”, “Initializing package states…”]}

    Reply
    • Get root sudo su then rm the file to resolve “Permission denied“. If still denied, chmod 777 then rm the file.

      $ sudo su
      $ chmod 777 /var/lib/dpkg/lock
      $ rm /var/lib/dpkg/lock
      

      Close the terminal window to drop back out of su.

      Reply
  5. 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.

    =)

    Reply
  6. 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

    Reply
  7. 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

    Reply
  8. 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.

    Reply
    • @Ganesh

      Ensure that your device is connected to the internet. You can test using ping, try to ping google.com or any popular servers.

      Reply
  9. Hi Sir,

    0% [Connecting to in.archive.ubuntu.com (2001:67c:1360:8001:
    

    it is coming like this after typing given commands.

    Reply
    • @srujan

      What commands in particular, just be a little clear on the question so we can help you easily. Hope you have understood.

      Reply
  10. Not able to update the python version from 2.7 to 3.6, it is showing error like this:

    $ sudo apt-get install python3.6Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    E: Unable to locate package python3.6
    E: Couldn't find any package by glob 'python3.6'
    E: Couldn't find any package by regex 'python3.6'
    
    Reply
  11. Hello, I have this issue too and it get fixed with this guide. But, the issue return each time the system startup. Any idea why is this happening?

    Reply
    • @Luis

      Try to use both approaches mentioned in the article, if they fail to work let us know, we will try to investigate.

      Reply
  12. Hi, I use Ubuntu 16.04, after i follow your step, the problem is solve but it come a new problem after input this command.

    $ sudo apt-get update..
    
    the problem is :
    E: Problem executing scripts APT::Update::Post-Invoke-Success 
    'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; 
    then appstreamcli refresh > /dev/null; fi'
    E: Sub-process returned an error code
    

    can you help me for solve this problem..?

    Reply
  13. Admin@san:~$ sudo kill -9 11555
    sudo: /etc/sudoers: Not a directory

    always telling this command sudo: /etc/sudoers: Not a directory..
    what I should do now?

    Reply
  14. The fix in the main post seems like a bit of overkill. Only the process actually owning the lock needs to be killed.

    You can find its PID with lsof:

    $ sudo lsof /var/lib/dpkg/lock
    

    Example output:

    lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
    Output information may be incomplete.
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    unattende 3002 root 4uW REG 8,10 0 1471282 /var/lib/dpkg/lock

    In this case, the PID is 3002, and “sudo kill 3002” or “sudo kill -9 3002” should release the lock.

    If lsof lists no process and the problem remains, the lock file may be safely deleted.

    Reply
  15. In general, it’s always best to try a simple kill without the -9 option first. This asks the process to exit normally, which allows it to clean up first. Only if the process fails to exit, meaning it’s hung, should you kill -9, which tells to kernel to terminate it.

    Reply

Got something to say? Join the discussion.

Thank you for taking the time to share your thoughts with us. We appreciate your decision to leave a comment and value your contribution to the discussion. It's important to note that we moderate all comments in accordance with our comment policy to ensure a respectful and constructive conversation.

Rest assured that your email address will remain private and will not be published or shared with anyone. We prioritize the privacy and security of our users.