Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    "consuming all the memory of the system and forcing the server to be crashed" ... The system must have been swapping heavily, giving the impression of non-responsiveness. Otherwise the OOM killer would have come out of retirement and taken care of the web server. Commented Jun 13, 2019 at 3:54
  • @muru The OOM killer might not have killed the webserver. Without knowing more detail about the way the web-server was divided into process, we really couldn't guess the /proc/pid/oom_score. The OOM killer isn't guaranteed to go after the troublesome program, especially where that program is composed of many smaller processes. Commented Jun 13, 2019 at 6:59
  • @PhilipCouling true, it might not, but if the webserver continues misbehaving, it will be killed eventually, once the OOM killer has run out of other targets Commented Jun 13, 2019 at 7:13