Return-Path: X-Original-To: apmail-httpd-users-de-archive@www.apache.org Delivered-To: apmail-httpd-users-de-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7845710CE3 for ; Mon, 5 Aug 2013 11:39:45 +0000 (UTC) Received: (qmail 38635 invoked by uid 500); 5 Aug 2013 11:39:45 -0000 Delivered-To: apmail-httpd-users-de-archive@httpd.apache.org Received: (qmail 35184 invoked by uid 500); 5 Aug 2013 11:39:40 -0000 Mailing-List: contact users-de-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users-de@httpd.apache.org List-Id: Delivered-To: mailing list users-de@httpd.apache.org Received: (qmail 34117 invoked by uid 99); 5 Aug 2013 11:39:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Aug 2013 11:39:39 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [83.246.67.243] (HELO c1.resellerdesktop.de) (83.246.67.243) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Aug 2013 11:39:31 +0000 Received: from p3ee2840b.dip0.t-ipconnect.de ([62.226.132.11] helo=[192.168.0.32]) by c1.resellerdesktop.de with esmtpa (Exim 4.76) (envelope-from ) id 1V6J7i-0006Fc-El for users-de@httpd.apache.org; Mon, 05 Aug 2013 13:38:50 +0200 Message-ID: <51FF8ECC.3040203@evolution-hosting.eu> Date: Mon, 05 Aug 2013 13:38:52 +0200 From: Apache Admin User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: users-de@httpd.apache.org Subject: Apache Hauptprozess =?ISO-8859-15?Q?fri=DFt_GBweise_Ram=2E?= Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Score: () X-Spam-Report: X-Virus-Checked: Checked by ClamAV on apache.org Hallo, ich habe einen httpd 2.4 dessen Hauptprozes GBweise Ram futtert und dann irgendwann zuviel Ram verbraucht: In diesem Fall die PID : 18154 # pstree -up | grep http |-httpd(18154)-+-httpd(849,apache) | |-httpd(1317,apache) | |-httpd(1333,apache) | |-httpd(1339,apache) | |-httpd(1377,apache) | |-httpd(2382,apache) nach dem Neustart hiers ganz ok aus ( 84 MB RAM ) : # top -c -b -n 1 | grep http ... PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6234 apache 20 0 137m 121m 3892 S 0,0 1,2 0:00.45 /usr/sbin/httpd - 7011 apache 20 0 137m 119m 1992 S 0,0 1,2 0:00.31 /usr/sbin/httpd - 7012 apache 20 0 137m 119m 1992 S 0,0 1,2 0:00.32 /usr/sbin/httpd - 18154 root 20 0 99060 84m 7424 S 0,0 0,8 0:11.62 /usr/sbin/httpd - 30228 apache 20 0 137m 121m 3964 S 0,0 1,2 0:01.27 /usr/sbin/httpd - nach ein paar Tagen sieht das dann so aus: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5911 root 20 0 712m 637m 529m S 0.0 6.3 20:33.78 /usr/sbin/httpd - 5911 root 20 0 712m 637m 529m S 0.0 6.3 20:33.79 /usr/sbin/httpd - 5911 root 20 0 712m 637m 529m S 0.0 6.3 20:34.07 /usr/sbin/httpd - 5911 root 20 0 712m 637m 529m S 0.0 6.3 20:34.10 /usr/sbin/httpd - 5911 root 20 0 712m 637m 529m S 0.0 6.3 20:34.14 /usr/sbin/httpd - 5911 root 20 0 712m 637m 529m S 0.0 6.3 20:34.15 /usr/sbin/httpd - 5911 root 20 0 712m 637m 529m S 0.0 6.3 20:34.50 /usr/sbin/httpd - 5911 root 20 0 712m 637m 529m S 0.0 6.3 20:34.78 /usr/sbin/httpd - 5911 root 20 0 712m 637m 529m S 0.0 6.3 20:35.05 /usr/sbin/httpd - 5911 root 20 0 712m 637m 529m S 0.0 6.3 20:35.50 /usr/sbin/httpd - .. einen Tag sp�ter so : PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5911 root 20 0 1312m 1.1g 990m S 0.0 11.0 46:38.54 /usr/sbin/httpd - 5911 root 20 0 1312m 1.1g 990m S 0.0 11.0 46:38.54 /usr/sbin/httpd - 5911 root 20 0 1312m 1.1g 990m S 0.0 11.0 46:38.83 /usr/sbin/httpd - 5911 root 20 0 1312m 1.1g 990m S 0.0 11.0 46:39.72 /usr/sbin/httpd - 5911 root 20 0 1312m 1.1g 990m S 0.0 11.0 46:40.27 /usr/sbin/httpd - 5911 root 20 0 1312m 1.1g 990m S 0.0 11.0 46:40.63 /usr/sbin/httpd - 5911 root 20 0 1312m 1.1g 990m S 0.0 11.0 46:40.79 /usr/sbin/httpd - 5911 root 20 0 1312m 1.1g 990m S 0.0 11.0 46:41.39 /usr/sbin/httpd - 5911 root 20 0 1312m 1.1g 990m S 0.0 11.0 46:41.56 /usr/sbin/httpd - .. noch einen Tag sp�ter: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5911 root 20 0 1919m 1.6g 1.5g S 0.0 16.4 77:41.20 /usr/sbin/httpd - 5911 root 20 0 1919m 1.6g 1.5g S 0.0 16.4 77:41.20 /usr/sbin/httpd - 5911 root 20 0 1919m 1.6g 1.5g S 0.0 16.4 77:41.20 /usr/sbin/httpd - 5911 root 20 0 1919m 1.6g 1.5g S 0.0 16.4 77:41.26 /usr/sbin/httpd - .. noch einen .. 5911 root 20 0 2523m 2.1g 2.0g S 0.0 21.7 111:58.41 /usr/sbin/httpd - 5911 root 20 0 2523m 2.1g 2.0g S 0.0 21.7 111:58.41 /usr/sbin/httpd - 5911 root 20 0 2523m 2.1g 2.0g S 0.0 21.7 111:58.42 /usr/sbin/httpd - .... bis es knallt : PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5911 root 20 0 2934m 2.5g 2.3g R 93.9 25.4 140:34.99 /usr/sbin/httpd - 5911 root 20 0 2948m 2.5g 2.3g R 44.1 25.5 140:58.68 /usr/sbin/httpd - 5911 root 20 0 2957m 2.5g 2.3g R 74.4 25.6 141:15.27 /usr/sbin/httpd - 5911 root 20 0 2962m 2.5g 2.3g R 41.7 25.6 141:30.79 /usr/sbin/httpd - 5911 root 20 0 2975m 2.5g 2.3g S 0.0 25.7 141:45.92 /usr/sbin/httpd - 5911 root 20 0 2982m 2.5g 2.3g R 55.3 25.8 142:01.15 /usr/sbin/httpd - 5911 root 20 0 2988m 2.6g 2.4g S 0.0 25.8 142:10.92 /usr/sbin/httpd - 5911 root 20 0 2999m 2.6g 2.4g R 97.6 25.9 142:30.79 /usr/sbin/httpd - 5911 root 20 0 3011m 2.6g 2.4g S 0.0 26.0 142:49.14 /usr/sbin/httpd - 5911 root 20 0 3017m 2.6g 2.4g R 55.8 26.1 143:01.17 /usr/sbin/httpd - 5911 root 20 0 3034m 2.6g 2.4g S 44.2 26.3 143:26.17 /usr/sbin/httpd - 5911 root 20 0 3039m 2.6g 2.4g S 0.0 26.3 143:39.87 /usr/sbin/httpd - 5911 root 20 0 3044m 2.6g 2.4g S 38.2 26.3 143:52.75 /usr/sbin/httpd - 5911 root 20 0 3050m 2.6g 2.4g S 0.0 26.4 144:14.60 /usr/sbin/httpd - 5911 root 20 0 3053m 2.6g 2.4g S 0.0 26.4 144:44.22 /usr/sbin/httpd - 5911 root 20 0 3058m 2.6g 2.4g S 0.0 26.5 145:10.60 /usr/sbin/httpd - 5911 root 20 0 3060m 2.6g 2.4g R 82.2 26.5 145:39.97 /usr/sbin/httpd - Hier war dann schlu� : da hat der OOM Killer zugeschlagen. Es gibt kein mod_php, kein mod_fastcgi in dem Apache . Kann es sein, da� Googles SpeedPage Modul da ggf. Schuld haben kann ? Oder ist das schon mal jemandem untergenommen? Komischerweise tritt es bevorzugt nachts auf, wenn die Backups laufen ( IO/CPU last ). Infos: # prefork MPM: Implements a non-threaded, pre-forking web server # See: http://httpd.apache.org/docs/2.4/mod/prefork.html LoadModule mpm_prefork_module modules/mod_mpm_prefork.so Server version: Apache/2.4.4 (Fedora) Server built: May 17 2013 12:21:45 Server hat 10 GB Ram. mit freundlichen Gr��en, Marius Schwarz --------------------------------------------------------------------- To unsubscribe, e-mail: users-de-unsubscribe@httpd.apache.org For additional commands, e-mail: users-de-help@httpd.apache.org