The information presented by htop will identify the processes responsible for high resource usage on the server. On informing the client, they in turn blocked that IP at the Cloudflare on our recommendation, so those continued requests then never even reached the server. On identifying this, I banned the IP at the server level, opened htop again, and almost instantly the CPU became mostly idle again. This massive amount of requests didn’t take the server or website down, but it was a serious problem that needed to be handled. The next step was checking the access logs to see what was going on, and in this case, it was one singular IP sending thousands upon thousands of requests every single second, loading anything and everything it could across the website. All 4 vCPUs were continually close to 100%, and the CPU usage was all tied to one specific site on the server. After connecting to the server to check what was going on I opened up htop. It was reporting that a server’s CPU usage was running at over 90%. Recently while working on support, I took on a 360 ticket which was automatically created through our server monitoring. An Example from Our Support Desk: Stopping a DoS Attack, Step by Step
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |