خرید بک لینک

Trying to debug an infrequent (albeit painful) oom-killed HTTP process on a Centos 6 box. I get the usual in logs:

Out of memory: Kill process 14466 (httpd) score 405 or sacrifice child

And the Apache logs confirm that the process died. Unfortunately this gets me nowhere closer to figuring out where in the code tree httpd goes awry. It's a fairly busy machine with a lot of users coecting to do things on a database-driven site (mod_perl). Given the normal ruing load it's not easily possible to correlate "this user did that" with the OOM event, especially since things seem to be ruing fine for days or weeks, and then suddenly one of the http threads goes splat.

What I'd like to get is a dump of state info for the PID oom-killer is about to terminate, rather than just the "oom-killed this process" after the fact. Is this possible?

برچسب: نویسنده: استخدام کار تاريخ: سه شنبه 8 تير 1395 ساعت: 7:56

صفحه بندی