Root 4667 1 0 12:12 ? 00:00:01 /usr/bin/python3 /usr/sbin/aptdįind out more about this package $ apt-file search /usr/sbin/aptd Get details on the process $ sudo ps -p 4667 -f
#LOCK ERROR SUDO APT GET INSTALL INSTALL#
NOTE: I recommend you whatever you try to keep of track/log of what commands are you applying, this precaution will help other to help you if something goes wrong.Troubleshoot "Could not get lock /var/lib/dpkg/lock" errors when trying to update or install debian packages Error Message E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)Į: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?įind out if a process has locked the file $ sudo lsof /var/lib/dpkg/lockĬOMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAMEĪptd 4667 root 8uW REG 252,3 0 131210 /var/lib/dpkg/lockĪnothe less precise way is to look for a likely process still running $ ps -e | grep -E '(apt)|(dpkg)' This should resume the process and keep everything stable. You should try to recover whatever you were installing at that moment with: sudo apt update To delete them use: sudo rm /var/lib/apt/lists/lock You could delete the dpkg lock files which you can double-check manually one by one with: sudo lsof /var/lib/dpkg/lock If you have only one output, something that finishes like: S+ 19:16 0:00 grep -color=auto -i apt Because if that is the case, you should wait for them to finish.Ĭhecking if some programs is locking dpkg files: ps aux | grep -i apt IMPORTANT: Check if some other process is locking dpkg files instead of deleting them immediately. This means that some program is updating the system or installing a new software. I couldn't, it says that: E: Could not get lock /var/lib/dpkg/lock Tried to update and upgrade: sudo apt update
I tried the solution of and didn't work for me.ĭelete the updates with: cd /var/lib/dpkg/updates
If I stop it, will I still get the dpkg error (on the off chance that I won't), or if so what do I need to to resume using apt-get commands and its Super Cow Powers? All up until: A lib/gemcache/ruby/1.9.1/gems/state_machine-1.1.2/gemfiles/active_record-2.1.2.gemfile.lock So on it goes for miles, talking about gem caches, rubies, & stuff I wish I had. Attempting to update the Metasploit Framework. opt/metasploit/postgresql/scripts/ctl.sh : postgresql (pid 1191) already running Rm: cannot remove `watobo-0.9.8.724.gem': No such file or directory The last bit of legible info was all this: Installing (ri/RDoc) documention for (stuff and such)ĮRROR: Could not find a valid gem 'watobo-0.9.8.724.gem' (>= 0) in any repository
#LOCK ERROR SUDO APT GET INSTALL UPGRADE#
I was running an upgrade with the apt-get command, and it was taking an exceptionally long time because half way through my ISP hit me in the face with their fair usage policy.Īfter sitting outside & watching the rain for awhile my electronics regained consciousness, so I went back to complete the upgrade and my terminal scolds me with "E: dpkg was interrupted, you must manually run 'sudo dpkg -configure -a' to correct the problem."
0 kommentar(er)
