apache2.service: Failed to run 'start' task: No space left on device [duplicate]
This question already has an answer here:
Root drive is running out of disk space. How can I free up space?
12 answers
How to get disk usage from command line?
2 answers
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?
server apache2
marked as duplicate by N0rbert, karel, Elder Geek, Charles Green, K7AAY Jan 30 at 19:10
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
Root drive is running out of disk space. How can I free up space?
12 answers
How to get disk usage from command line?
2 answers
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?
server apache2
marked as duplicate by N0rbert, karel, Elder Geek, Charles Green, K7AAY Jan 30 at 19:10
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
2
'/' is full, so you have to hunt down the biggies./var/log
would be the place to start.
– xenoid
Jan 28 at 21:21
@xenoid how do i inspect/var/log
and delete files?
– laukok
Jan 28 at 22:06
add a comment |
This question already has an answer here:
Root drive is running out of disk space. How can I free up space?
12 answers
How to get disk usage from command line?
2 answers
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?
server apache2
This question already has an answer here:
Root drive is running out of disk space. How can I free up space?
12 answers
How to get disk usage from command line?
2 answers
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?
This question already has an answer here:
Root drive is running out of disk space. How can I free up space?
12 answers
How to get disk usage from command line?
2 answers
server apache2
server apache2
edited Jan 28 at 21:25
laukok
asked Jan 28 at 20:49
laukoklaukok
64151635
64151635
marked as duplicate by N0rbert, karel, Elder Geek, Charles Green, K7AAY Jan 30 at 19:10
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by N0rbert, karel, Elder Geek, Charles Green, K7AAY Jan 30 at 19:10
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
2
'/' is full, so you have to hunt down the biggies./var/log
would be the place to start.
– xenoid
Jan 28 at 21:21
@xenoid how do i inspect/var/log
and delete files?
– laukok
Jan 28 at 22:06
add a comment |
2
'/' is full, so you have to hunt down the biggies./var/log
would be the place to start.
– xenoid
Jan 28 at 21:21
@xenoid how do i inspect/var/log
and delete files?
– laukok
Jan 28 at 22:06
2
2
'/' is full, so you have to hunt down the biggies.
/var/log
would be the place to start.– xenoid
Jan 28 at 21:21
'/' is full, so you have to hunt down the biggies.
/var/log
would be the place to start.– xenoid
Jan 28 at 21:21
@xenoid how do i inspect
/var/log
and delete files?– laukok
Jan 28 at 22:06
@xenoid how do i inspect
/var/log
and delete files?– laukok
Jan 28 at 22:06
add a comment |
2 Answers
2
active
oldest
votes
Your disk is full. You need to delete some files.
What and how should I delete?
– laukok
Jan 28 at 21:25
cyberciti.biz/faq/check-free-space There are GUIs that allow you to get a picture of what is taking up all the space.
– user459652
Jan 28 at 21:30
thanks. still no clue what to delete. i barely use this hosting server. how is it running out space?
– laukok
Jan 28 at 22:03
add a comment |
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.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your disk is full. You need to delete some files.
What and how should I delete?
– laukok
Jan 28 at 21:25
cyberciti.biz/faq/check-free-space There are GUIs that allow you to get a picture of what is taking up all the space.
– user459652
Jan 28 at 21:30
thanks. still no clue what to delete. i barely use this hosting server. how is it running out space?
– laukok
Jan 28 at 22:03
add a comment |
Your disk is full. You need to delete some files.
What and how should I delete?
– laukok
Jan 28 at 21:25
cyberciti.biz/faq/check-free-space There are GUIs that allow you to get a picture of what is taking up all the space.
– user459652
Jan 28 at 21:30
thanks. still no clue what to delete. i barely use this hosting server. how is it running out space?
– laukok
Jan 28 at 22:03
add a comment |
Your disk is full. You need to delete some files.
Your disk is full. You need to delete some files.
answered Jan 28 at 21:24
roadmrroadmr
27.5k56479
27.5k56479
What and how should I delete?
– laukok
Jan 28 at 21:25
cyberciti.biz/faq/check-free-space There are GUIs that allow you to get a picture of what is taking up all the space.
– user459652
Jan 28 at 21:30
thanks. still no clue what to delete. i barely use this hosting server. how is it running out space?
– laukok
Jan 28 at 22:03
add a comment |
What and how should I delete?
– laukok
Jan 28 at 21:25
cyberciti.biz/faq/check-free-space There are GUIs that allow you to get a picture of what is taking up all the space.
– user459652
Jan 28 at 21:30
thanks. still no clue what to delete. i barely use this hosting server. how is it running out space?
– laukok
Jan 28 at 22:03
What and how should I delete?
– laukok
Jan 28 at 21:25
What and how should I delete?
– laukok
Jan 28 at 21:25
cyberciti.biz/faq/check-free-space There are GUIs that allow you to get a picture of what is taking up all the space.
– user459652
Jan 28 at 21:30
cyberciti.biz/faq/check-free-space There are GUIs that allow you to get a picture of what is taking up all the space.
– user459652
Jan 28 at 21:30
thanks. still no clue what to delete. i barely use this hosting server. how is it running out space?
– laukok
Jan 28 at 22:03
thanks. still no clue what to delete. i barely use this hosting server. how is it running out space?
– laukok
Jan 28 at 22:03
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered Jan 29 at 1:20
xenoidxenoid
1,8731416
1,8731416
add a comment |
add a comment |
2
'/' is full, so you have to hunt down the biggies.
/var/log
would be the place to start.– xenoid
Jan 28 at 21:21
@xenoid how do i inspect
/var/log
and delete files?– laukok
Jan 28 at 22:06