0

I am trying to restart my Apache but I keep getting this error:

Jan 28 20:34:05 localhost systemd[1]: apache2.service: Failed with result 'resources'.
Jan 28 20:36:22 localhost systemd[1]: apache2.service: Failed to run 'start' task: No space left on device
Jan 28 20:36:22 localhost systemd[1]: Failed to start The Apache HTTP Server.
Jan 28 20:36:22 localhost systemd[1]: apache2.service: Failed with result 'resources'.
Jan 28 20:37:37 localhost systemd[1]: apache2.service: Failed to run 'start' task: No space left on device
Jan 28 20:37:37 localhost systemd[1]: Failed to start The Apache HTTP Server.
Jan 28 20:37:37 localhost systemd[1]: apache2.service: Failed with result 'resources'.
Jan 28 20:45:03 localhost systemd[1]: apache2.service: Failed to run 'start' task: No space left on device
Jan 28 20:45:03 localhost systemd[1]: Failed to start The Apache HTTP Server.
Jan 28 20:45:03 localhost systemd[1]: apache2.service: Failed with result 'resources'.

I have tried this solution but it does not work:

fs.inotify.max_user_watches = 262144 (Add this to /etc/sysctl.conf and then run sysctl -p.)

This is some more info if it helps?

sudo df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        20G   20G     0 100% /
devtmpfs        488M     0  488M   0% /dev
tmpfs           490M     0  490M   0% /dev/shm
tmpfs           490M   51M  440M  11% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           490M     0  490M   0% /sys/fs/cgroup
tmpfs            98M     0   98M   0% /run/user/0

Any ideas what I can do?

EDIT:

There is no solution from this answer. How is this duplicated?

Run
  • 2,748

2 Answers2

1

Your disk is full. You need to delete some files.

roadmr
  • 34,802
1

So your disk is full...

Without a GUI, do du -m / | sort -n and the last lines are going to be the bigger directories. Typically you are looking for:

  • logs accumulating in /var/log and its subdirectories. The system doesn't need them, and you can erase the oldest (or better set up cron job or services to perform log rotation).
  • random files created in /tmp (can usually be erased on sight if nothing is running)
  • a bloated database /var/lib/mysql/*. Don't erase them directly, inspect the DB for figure out where this comes from, and if necessary use the DB system to truncate the relevant tables.
  • random files created as uploads in /var/www (or wherever the Apache content directory is)
  • random files created elsewhere, but this would be server specific.

These last two require to understand why they are created and whether you can erase them.

But of course this can happen again unless you add periodic script/services to remove these excess files.

xenoid
  • 5,759