VDS wont install LAMP Stack

[justin2234]

So i purchased my third unmanaged linux vds and was going to do a LAMP stack on Ubuntu 16.04 (my previous machines had ubuntu 14 and 15)
I logged in and did apt-get update, then proceeded with apt install apache2 and already had issues.
https://i.gyazo.com/2ab292531703e685dbf ... e0c542.png
Never had this issue before as i've done this on 2 other machines with no problem. Any solution ?

[$atanic $pirit]

That error got nothing to do with LAMP. That simply means that dpkg failed to process the updated kernel package. Run these commands and see, if they help.

Code: Select all

apt-get install linux-image-generic
apt-get -f install

That should do the trick, but if it still fails then you need to purge the half installed package and try to install it from beginning. These commands would do that trick for you, if the case may be.

Warning: Make sure you are not purging the currently used kernel. You can check the current kernel version with "uname -r" command in putty.

Code: Select all

apt-get purge linux-image-extra-4.4.0-28-generic

[Edge100x]

It appears that your boot partition may be full. You should be able to confirm this with the output of "df" -- look for "/boot" there and see if the amount free is small (less than 50 MB would likely indicate a problem).

To clean things up, you could try:

Code: Select all

apt-get autoclean

If that doesn't work, you could manually delete old kernels in /boot. First, find out what your current kernel is with "uname -r", and then "rm" the files for older kernels in /boot (using the purge command that SS mentioned may also work). Back up your files before rebooting again, to be safe.

As of today, our Ubuntu 16.04 installer puts everything in a single partition. If you don't have many customizations on your VDS, you might also reinstall with that.

[$atanic $pirit]

If that doesn't work, you could manually delete old kernels in /boot. First, find out what your current kernel is with "uname -r", and then "rm" the files for older kernels in /boot (using the purge command that SS mentioned may also work). Back up your files before rebooting again, to be safe.

I would highly recommend against manually using the rm command in this case. /boot directory is a sensitive one, and you may end up destroying your system. Its much better to use purge on the kernel, if you want to get rid of the old ones.

[Edge100x]

I would highly recommend against manually using the rm command in this case. /boot directory is a sensitive one, and you may end up destroying your system. Its much better to use purge on the kernel, if you want to get rid of the old ones.

It would be difficult to destroy the system by deleting old kernels. It is possible that the user could make the system unbootable and need to boot from CD. But, that is easily avoided, and the risk is similar to using purge.

Since he started with "So i purchased my third unmanaged linux vds," it sounds like this is a new installation. I'd recommend reinstalling the OS as the best course of action, since it will avoid the potential of the partition filling up again in the future.

[$atanic $pirit]

Purge would clean off headers, and config files along with the kernel, as opposed to deleting everything one by one. Leaving all that in boot dir would only cause future problems.