- Jun 10, 2017
- 10,845
- 15,962
I'm sure that you can have a better view of the stats. Even with a server at full charge, it's not this common that the CPU end at 100% before the net (not the bandwidth but the number of slots) ; or at least it wasn't back in my times. So...cpu always hit 100%, i don't know why...
There's little to none reason for the HTTP server to be the cause of this. Especially nginx that's designed do keep its usage relatively low.
Same for the SQL server. Unless you limited its memory usage, the RAM should normally be impacted before the CPU.
It can be the CPU itself if its dying, but you should have seen other signs than just a 100% usage.
This let the scripts. And the only reason I see right now for such CPU use is an endless loop somewhere.
Or the whole server have been compromised, and you've a parasite process. But even if it's a crappy wrote things, the net usage should reach its limit before the CPU, since the goal stay to spread itself or turn the server as ghost host in a botnet.
There's no reason for this unless you changed something. Personally I would try to solve this issue first. Whatever make it impossible to works have chance to be the cause of the whole problem. And even if it's not the cause, it would revert the whole server to a familiar configuration, which is always better.I remember that I installed one PHP extension called "memcached", and it worked very well, but I can't get it work anymore...