One of STORM's key benefits is that it remotely manages servers. This enables management of multiple servers from a single application, it also enables sites to be faster as it doesn't use a resource footprint on the servers. This does mean though, that a very small amount of free space is required on the servers so that STORM can send tasks to them.


When a server runs out of disk space STORM disables all features for that server as it would not be possible to run them.


Please keep an eye out for disk notifications to ensure that this doesn't happen.


If it does happen, not only will STORM stop working for you but your sites will likely stop working too. So you are going to want to delete some data, maybe some old or dev sites. Trouble is that you cannot delete them via STORM as you are out of space.


So what do you do...


The good news is that you just need to free a small amount of space for STORM to enable the features again, then you'll be able to delete entire unused sites via a click in STORM. But how do you delete any amount of data.


The best method is via FTP, if you have an unused site then you can connect to that and delete at will. See the guide below for accessing FTP for a site.


https://support.nimbushosting.co.uk/support/solutions/articles/36000020515-accessing-your-ftp-details


If you don't have any unused sites, you may be able to find some unrequired files via FTP.


Nothing to delete in a website?  Another option is to check the server via SSH. See some steps below:


The easiest way of checking this is to issue this command:



  • df -h


and the output should look similar to below:



Filesystem                         Size  Used Avail Use% Mounted on udev                               975M     0  975M   0% /dev tmpfs                              200M   24M  176M  12% /run /dev/mapper/ubuntu--base--vg-root   33G  3.1G   28G  10% / tmpfs                              996M  4.0K  996M   1% /dev/shm tmpfs                              5.0M     0  5.0M   0% /run/lock tmpfs                              996M     0  996M   0% /sys/fs/cgroup /dev/xvda1                         472M  110M  339M  25% /boot tmpfs                              200M     0  200M   0% /run/user/1003


In this example the one you want to pay attention to is the 33G partition, generally it will always be the largest partition you want to make sure has free space.


If the drive is 100% full you will need to try and clear some space to get back up and running again, the easiest way is to clear some log files, these logs are safe to clear:



  • /home/storm/logs/SITENAME/
  • /var/log/


It's best to clear out the archived logs in /var/log first by issuing this command:



rm -rf /var/log/*.gz