Your VPS your dedicated server has run out of disk space
You've run out of disk space on your dedicated server or virtual private server (VPS)
This could exhibit itself in many ways, but if you're using mail services hosted with Postfix on the server, one of the first things you'll probably see is emails with the subject "Postfix SMTP Errors" and body like this:
Transcript of session follows. Out: 220 [YOUR_SERVER] ESMTP Postfix In: EHLO [SENDING_SERVER] Out: 250-[YOUR_SERVER] Out: 250-PIPELINING Out: 250-SIZE 51200000 Out: 250-ETRN Out: 250-STARTTLS Out: 250-AUTH CRAM-MD5 LOGIN PLAIN Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: MAIL FROM:<FROM_ADDRESS> BODY=8BITMIME Out: 452 4.3.1 Insufficient system storage
There are two ways to proceed:
1) Simply Upgrade your storage resources
You can do that from within the Websavers Client Centre. Choose Manage beside your VPS, then under Configuration, change it so you have more storage.
2) Find the source and remove the larger data
If you don't have any information to go on as to what might have caused your storage to fill up so abruptly, then you'll need to find the source of the problem first. If you are using Plesk, you can use this guide to learn what's using a lot of storage. If you aren't using a control panel or if Plesk isn't showing everything clearly enough for you, then you'll need to do some command line sleuthing. Connect via console / ssh and proceed as follows for CentOS. Other package managers will likely have the ncdu program as well:
yum install ncdu --enablerepo-epel
Once installed, run it:
It will quick scan your system and provide you with a breakdown of storage usage on the system. From there you can navigate through the folder structure with the arrow keys on your keyboard, looking for anything unusually large. Note: If you're using Plesk, it's *always* best to try using Plesk to find the large files first prior to falling back to command line options. This is because removing files out from under Plesk can cause inconsistencies in the Plesk database.
Here are some common reasons for high storage usage and solutions to them:
- Backup Storage: look at your backups and perhaps remove some older ones, or set your backup solution to store your backups in cloud storage like Dropbox. If you're using Plesk, you can learn how to do that here.
- Logs: If you've identified that the storage is being used by large log files, take a skim over the logs to learn why -- the errors within should indicate why they're being reported in the log file. For example, if the reason for the excessive logging is because you need to turn down the loglevel, you could read the manual for the application and learn how to turn down the amount of logging in the app's config file. If the reason is that there's a bug or problem with the way your software is being used, you would then need to fix that issue. Alternatively, if the logging appears normal, then you may need to report the bug to the developers of the software and ask them to implement an appopriate logrotate script into the package that was installed on the server or edit the existing one to increase its log rotation frequency.
- 0 Users Found This Useful