Question
I cannot connect to my droplet and it's CPU usage is over 90%
- Posted March 30, 2017
- VPNConfiguration ManagementControl PanelsUbuntu 16.04
I’m using the SFO1 server, Ubuntu 16.04.2 x64, and installed a proxy called shadowsocks. The problem I have is the connection to this droplet would somehow be crashed. I cannot connect to the droplet using either Putty or Digitalocean console. And when I go to the droplet page, I see a over 90% CPU rate.
Does anyone know how to solve this issue? I’m really novice and not a programmer at all… Let me know if you need more intel to know what’s going on here…
Many thanks.
Subscribe
Share
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!
Sign in to AnswerThese 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.
Try DigitalOcean for free
Click below to sign up and get $100 of credit to try our products over 60 days!
I’m not sure. It seems like the official Python release is the old one. Have a look at https://github.com/shadowsocks/shadowsocks-libev - it the pure C version and it seems to be more updated. I don’t know anything about shadowsocks - I’m simply just looking at their github page.
Which version of shadowsocks are you running?
@bluesagittary
If the CPU usage is spiking, it could be that the software you’re running is extremely intensive for the size of Droplet you’re using, or it’s disk intensive, causing CPU to spike due to higher I/O leading to higher wait times.
If you’re experiencing delays connecting to SSH, either of those scenarios could be the reason.
We’d need to take a look at the output of the
topcommand to get a clear look at usage. If you can run:Then hit
SHIFT+M, followed byc, thenewe can see the sorted process listing. You may very well need to reboot the server for this to work since you’re not able to connect right now.Unfortunately, it looks like your only option is to reboot the server. There should be a button in the droplet page.