Question
Site just died out of the blue - not even sure how to debug what happened
I setup a 10$/mo droplet, running a WordPress install.
Things went smoothly, I encountered no issues and was able to get everything setup quite easily.
fast forward 23 days, and my site is now hitting a 504 - Gateway Time-Out error.
I reached out to the digital ocean staff (not expecting to get much help - which I didn’t) and was told to run ‘top’ to check what processes are running on the server.
Yesterday, around 7:00PM EST, I can see in the chart that’s when my CPU usage started jumping from about 15-22% to 100+%. I haven’t logged into the site, sshed in, ftped in, made any alterations etc.
I’m wondering why would my site just start spiking north of 100%, when I’m not receiving any more traffic than I normally am.
I’m at a loss here - and the sites been down for over 24 hours now, and I’ve made little to no progress in debugging it.
Thinking it might be time to call it quits and transfer away from DO - due to the down times.
Thanks to anyone who is willing to shead some light.
Graph Screenshot:
https://cldup.com/o-1AVekaMv.png
You can see, that in the past day is when everything started going haywire.
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.
×
Did you run ‘top’ to see what processes are running on the server?
@gparent I did, here is the output: https://cldup.com/MG2Xb7kK8g.png
Lots of php-fpm instances running . CPU is around 80%, but the numbers don’t add up with what is listed in ‘top’.
80 divided by 3.7 ~== 20 which seems to match the number of processes in your screenshot, or is at least close enough. I would check your web server’s access and error logs for the requests that those PHP-FPM processes are handling, and see if they are normal or if you’re under some sort of attack.
@gparent How do you block ALL incoming GET requests?
You could turn off your web server with
service nginx stop