How to safely abort apt-get install?

apt

I have an apt-get install process that seems to be hopelessly wedged at the processing triggers for python-support step.

My inclination is to kill it, but in the past, simply kill-ing an apt-get install process has caused me much grief. (IIRC assorted lock files are left behind, etc.)

Is there a safer way to stop this process?

Solution 1:

Killing processes

Generally speaking for killing a process, there's no safer way to kill a process than with a regular kill (SIGTERM). In case it's an interactive process it usually allows you to stop it even safer by sending a SIGINT signal, usually sent by pressing Ctrl + C. This signal is being trapped by the process itself can listen to it - and usually stop gracefully. ^{(thanks Eliah)}

DPKG database

Regarding the package management is a sort of special case. The DPKG database that the APT commands use under water can always detect whether an operation hasn't finished. Every package has an actual state which is marked in as well as a current state, e.g. unpacked, configured, etc. By killing the APT frontend, the database will be in a broken, but in known state. The lock files will only be released once it's all back in a clean state - you should get this fixed until it allows new operations.

The way to fix is just firing a process to get all packages in the configured state. Practically speaking, if you've interrupted an apt-get operation, you can just finish it later using

sudo dpkg --configure -a

It knows how to recover from the broken state to an all-configured state and in that sense just continue from where it was interrupted. The lock files are left there until you finished that, and that's for a reason - to prevent new operations with the DPKG database in an unclean state.

About SIGKILL (9)

Sending a SIGKILL (decimal representation 9) is very unsafe. This signal is not catched by the process, but the whole process will be cleaned up by the operating system (kernel) whether the process likes it or not. The state of the files on the file system can be left in a corrupt state. Never send these signals unless it's not listening to other more graceful signals anymore.

Solution 2:

When I encounter a failure with apt-get, I do the following (as root, i.e. sudo before all commands):

Kill the process named apt-get:
```
killall -9 apt-get
```
Reconfigure dpkg:
```
dpkg --configure -a
```
Update apt-get:
```
apt-get update
```
Update packages, including those improperly installed:
```
apt-get upgrade
```

This I learned from somewhere, but unfortunately I cannot remember exactly where.

Solution 3:

sudo dpkg -r <package name>

In my case I had problems with Java 8 on Ubuntu 12.04, so...

sudo dpkg -r oracle-java8-installer

Solution 4:

Linux and other Unix type systems are very powerful from the command line but very unforgiving once a process has started. Sending a process the kill signal will certainly kill the process that is running but bear in mind that you are leaving a database in an unstable state. The last record may not be closed out correctly so you risk have to repair a database. Not just with apt but with any application.

Always try to end the application in a normal manner and only kill processes that are run away applications.