server keeps getting error - seems disk full related

First try to find the largest files, maybe you have a huge log file or something else that is bugging this!

Source: https://www.tecmint.com/find-top-large-directories-and-files-sizes-in-linux/

That should already help you out a little bit! Let me know if you find anything.

If that isn't the problem we can discuss any other options

Thanks for the reply. I followed the command but get the following write failed: /tmp/sorteKHzE4: No space left on device

That was after running du -a /home | sort -n -r | head -n 5 if I run du -hs * | sort -rh | head -5 It gives me the following

6.4G    walkiees.co.uk
142M    staging.walkiees.co.uk
20K nginx-partials
4.0K    imagick3.4.3-PHP7.1-forge.sh

Which is what I would expect. When I run df -h I get

/dev/root        30G   28G     0 100% /
devtmpfs        987M     0  987M   0% /dev
tmpfs           990M  4.0K  990M   1% /dev/shm
tmpfs           990M  8.7M  981M   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           990M     0  990M   0% /sys/fs/cgroup
tmpfs           198M     0  198M   0% /run/user/1000

So 6gb is a lot for a website! Do you save all the files on that server?

Normally if you need to handle large files you use a separate service to store them like Amazon S3. For now I can only suggest you to either move the files to S3 or increase the volume of your server.

You can look in the walkiees.co.uk directory and see if you can find huge files there. A good place to start clearing would be storage/logs and check if you have large files there!

I do have assets (images) stored locally rather than S3. Just not something I have got round to doing. It's roughly 6GB of local assets so that makes sense.

I was struggling to debug it so I ended up deleting the server and provisioning a new one.

Just finished getting it all back up and running and it all seems OK. Have set it back up with just the single site. What's odd is that when I check the sizes again using df -h it shows the following...

udev            1.9G     0  1.9G   0% /dev
tmpfs           395M  6.5M  388M   2% /run
/dev/sda         79G   12G   63G  16% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
tmpfs           395M     0  395M   0% /run/user/1000

So it looks like the site is taking up double what it should be. Not sure why?

I had this issue before on my AWS hosting account. Turned out the permissions of my cache folder werent set up properly so even when doing php artisan clear:cache . The cache files were not being cleared. It kept growing and growing. What worked for me was changing the file ownership recursively for the cache folder.