Home / server / Questions / 418813
Accepted
db_ch
Asked: 2012-08-18 15:35:27 +0800 CST

Apache : with Googlebot connections, a single process takes all server memory

  • 772

Following https://serverfault.com/questions/418735/unbelievable-issue-a-single-apache-process-takes-4-gb-of-memory I post as a new question because I was able to identify the fact that it happens when the client connecting is Googlebot.

By "it", I mean that one single apache process eats 5 Gigabyte of memory ?!

Does anyone has an idea about what could be the cause of this ?

Thanks a lot for any help !

I found another question with exact same problem but no answer : https://serverfault.com/questions/161478/apache-process-consuming-all-memory-on-the-server

Our environment uses PHP and postgresql :

# httpd -V
Server version: Apache/2.2.3
Server built:   Jun  6 2012 10:00:42
Server's Module Magic Number: 20051115:3
Server loaded:  APR 1.2.7, APR-Util 1.2.7
Compiled using: APR 1.2.7, APR-Util 1.2.7
Architecture:   64-bit
Server MPM:     Prefork
  threaded:     no
    forked:     yes (variable process count)
Server compiled with....
 -D APACHE_MPM_DIR="server/mpm/prefork"
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_SYSVSEM_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=128
 -D HTTPD_ROOT="/etc/httpd"
 -D SUEXEC_BIN="/usr/sbin/suexec"
 -D DEFAULT_PIDLOG="run/httpd.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_LOCKFILE="logs/accept.lock"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="conf/mime.types"
 -D SERVER_CONFIG_FILE="conf/httpd.conf"
apache-2.2

1 Answers

  1. Best Answer

    Finally we found a solution, but not by looking in the logs !

    It was completely impossible to understand the cause of the problem by any possible solution. Even with core dumps or straces, no rational analysis succeeded !

    Until now, even with the problem solved I still cannot understand where the problem really came from and/or how to understand of analyze it. Therefore it's really difficult to give you any warranty that our solution was really the solution !

    As far as I know the solution seems to be MaxRequestsPerChild : ServerFault post about MaxRequestsPerChild

    • 1