Something is going on in my droplet...

To start, I am sorry for such title that doesn’t give any information about the problem.

I was checking a site on one of my droplets and couldn’t login to wordpress and cvplab.

Then I logged in using Putty and updated the server.

Now I see memory usage is “95.1% of 29.40GB”;

I am trying to log in to CPVlab, it says: Could not open database connection

Should I migrate to a new server?

I see I am not the only one having this problem:


Awesome, thanks for replies. I restored January backup and things are working fine now.

Thanks Jon, I was going to ask it.

The only problem is the disk usage, my CPVLab site log file takes 23GB space at /var/log/nginx

Can I delete it?

You may also want to look at your current disk usage. The command I like to use to find folders that are using the disk space is:

  1. cd /
  2. du -ck | sort -n | tail

Happy coding,

Jon Schwenn Platform Support Specialist DigitalOcean

You may need to temporarily disable your website to be able to make the repairs mentioned in the tutorial on preventing the xmlrpc attack. If you’re familiar with enabling/disabling ports using your firewall software, then use that to temporarily disable your http and https ports. Another method is to temporarily make the xmlrpc.php file not readable. Just remember to undo your temporary measures after following the tutorial.

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hey there fvin,

I see that you were able to get a backup restored and be up and running. As for your question about the log file and whether you can delete it - that is really up to you. Do you use that log for anything? Do any web analytics with it? If so, you probably do not want to delete it and would need to figure out some sort of log storage solution. If you don’t need it, you should probably just clear it instead of deleting it. This can be done with:

echo "" > /path/to/log/file/here

A good idea might be to look into logrotate to try to control these log file sizes for the future!