Sometime out of nowhere a droplet start lagging.
To a point where connecting via ssh can take up to 30-45secondes, and once connected each keystore take 1-2secondes to show. And this will fix itself after maybe 5-10minutes.

I tried to look at the cpu / memory usage history and everything look normal. It happend on many of my droplets.

The dmesg and syslog all look clean, and sadly digitalocean support say that there is no problem with the network / supervisor.

In the past, I asked digitalocean to migrate my droplet to a other server, and it mostly fix the problem, but later started to do the same thing on an other droplet.

I believe the problem is abore my droplets, so there is no logs I can produre to prove that there is a problem, and digitalocean don’t see anything wrong on their ends.

All I know is that sometime, the website become so slow, and then just crash since it take too long to responds, and when I try to connect via ssh to see what is happening, it take forever.

What else can I do?

Thank you

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.

Submit an Answer
1 answer

Hello, Vaielab

What you can do is to examine the logs for killed processes and also out of memory entries. To check this you can run the following commands:

  • grep -i kill /var/log/messages
  • grep -i `oom` /var/log/mesaages

I will also recommend using sar to examine the resources usage on the droplet. You can check the following article and also check the question for installing and using sar:

Hope that this helps!

by Justin Ellingwood
Monitoring a server's resources is an important task for every administrator. There are many command line tools made for this purpose. This guide will cover some of the more popular utilities for monitoring your VPS.