Bug#421557: marked as done (apache2: increasing memory usage)
Your message dated Sat, 16 Feb 2008 12:17:00 + with message-id [EMAIL PROTECTED] and subject line Bug#421557: fixed in apache2 2.2.3-4+etch4 has caused the Debian Bug report #421557, regarding apache2: increasing memory usage to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 421557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421557 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: apache2 Version: 2.2.3-4 Severity: normal Apache2's memory usage on a low traffic server keeps on increasing until it brings the whole server the down. Starts with: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 23865 0.1 1.6 23076 8448 ?Ss 04:44 0:00 /usr/sbin/apache2 -k start www-data 23870 0.5 3.4 33052 17532 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23871 0.5 3.5 33040 17916 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23872 0.0 1.3 23476 6860 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23873 0.0 0.8 23076 4072 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23874 0.0 0.8 23076 4084 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23877 0.0 0.8 23076 4072 ?S04:44 0:00 /usr/sbin/apache2 -k start A bit later: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1290 0.0 0.7 23076 3900 ?Ss Apr29 0:00 /usr/sbin/apache2 -k start www-data 1764 0.2 8.5 183828 43596 ?SApr29 3:45 /usr/sbin/apache2 -k start www-data 11452 0.1 9.7 104596 49512 ?SApr29 1:42 /usr/sbin/apache2 -k start www-data 11453 0.2 9.2 106980 47184 ?SApr29 2:06 /usr/sbin/apache2 -k start www-data 11462 0.2 9.4 106444 48056 ?SApr29 1:56 /usr/sbin/apache2 -k start www-data 18776 0.0 5.4 42888 27500 ?SApr29 0:18 /usr/sbin/apache2 -k start www-data 18777 0.1 6.6 49260 33920 ?SApr29 0:24 /usr/sbin/apache2 -k start www-data 18778 0.0 6.1 46496 31116 ?SApr29 0:17 /usr/sbin/apache2 -k start www-data 18779 0.1 6.1 46780 31148 ?SApr29 0:31 /usr/sbin/apache2 -k start www-data 18781 0.0 6.1 46968 31532 ?SApr29 0:21 /usr/sbin/apache2 -k start www-data 18782 0.1 5.7 44612 29160 ?SApr29 0:21 /usr/sbin/apache2 -k start The installation is quite standard, with modules php5, psql auth, and webdav enabled. Cheers, Chris. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.20-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages apache2 depends on: ii apache2-mpm-prefork 2.2.3-4Traditional model for Apache HTTPD apache2 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: apache2 Source-Version: 2.2.3-4+etch4 We believe that the bug you reported is fixed in the latest version of apache2, which is due to be installed in the Debian FTP archive: apache2-doc_2.2.3-4+etch4_all.deb to pool/main/a/apache2/apache2-doc_2.2.3-4+etch4_all.deb apache2-mpm-event_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-mpm-event_2.2.3-4+etch4_i386.deb apache2-mpm-perchild_2.2.3-4+etch4_all.deb to pool/main/a/apache2/apache2-mpm-perchild_2.2.3-4+etch4_all.deb apache2-mpm-prefork_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-mpm-prefork_2.2.3-4+etch4_i386.deb apache2-mpm-worker_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-mpm-worker_2.2.3-4+etch4_i386.deb apache2-prefork-dev_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-prefork-dev_2.2.3-4+etch4_i386.deb apache2-src_2.2.3-4+etch4_all.deb to pool/main/a/apache2/apache2-src_2.2.3-4+etch4_all.deb apache2-threaded-dev_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-threaded-dev_2.2.3-4+etch4_i386.deb apache2-utils_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-utils_2.2.3-4+etch4_i386.deb apache2.2-common_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2.2-common_2.2.3-4+etch4_i386.deb apache2_2.2.3-4+etch4.diff.gz to pool/main/a/apache2/apache2_2.2.3-4+etch4.diff.gz apache2_2.2.3-4+etch4.dsc to pool/main/a/apache2/apache2_2.2.3-4+etch4.dsc apache2_2.2.3-4+etch4_all.deb to pool/main/a/apache2/apache2_2.2.3-4+etch4_all.deb A summary of the changes between this
Bug#421557: marked as done (apache2: increasing memory usage)
Your message dated Thu, 31 Jan 2008 07:52:14 + with message-id [EMAIL PROTECTED] and subject line Bug#421557: fixed in apache2 2.2.3-4+etch4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: apache2 Version: 2.2.3-4 Severity: normal Apache2's memory usage on a low traffic server keeps on increasing until it brings the whole server the down. Starts with: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 23865 0.1 1.6 23076 8448 ?Ss 04:44 0:00 /usr/sbin/apache2 -k start www-data 23870 0.5 3.4 33052 17532 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23871 0.5 3.5 33040 17916 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23872 0.0 1.3 23476 6860 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23873 0.0 0.8 23076 4072 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23874 0.0 0.8 23076 4084 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23877 0.0 0.8 23076 4072 ?S04:44 0:00 /usr/sbin/apache2 -k start A bit later: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1290 0.0 0.7 23076 3900 ?Ss Apr29 0:00 /usr/sbin/apache2 -k start www-data 1764 0.2 8.5 183828 43596 ?SApr29 3:45 /usr/sbin/apache2 -k start www-data 11452 0.1 9.7 104596 49512 ?SApr29 1:42 /usr/sbin/apache2 -k start www-data 11453 0.2 9.2 106980 47184 ?SApr29 2:06 /usr/sbin/apache2 -k start www-data 11462 0.2 9.4 106444 48056 ?SApr29 1:56 /usr/sbin/apache2 -k start www-data 18776 0.0 5.4 42888 27500 ?SApr29 0:18 /usr/sbin/apache2 -k start www-data 18777 0.1 6.6 49260 33920 ?SApr29 0:24 /usr/sbin/apache2 -k start www-data 18778 0.0 6.1 46496 31116 ?SApr29 0:17 /usr/sbin/apache2 -k start www-data 18779 0.1 6.1 46780 31148 ?SApr29 0:31 /usr/sbin/apache2 -k start www-data 18781 0.0 6.1 46968 31532 ?SApr29 0:21 /usr/sbin/apache2 -k start www-data 18782 0.1 5.7 44612 29160 ?SApr29 0:21 /usr/sbin/apache2 -k start The installation is quite standard, with modules php5, psql auth, and webdav enabled. Cheers, Chris. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.20-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages apache2 depends on: ii apache2-mpm-prefork 2.2.3-4Traditional model for Apache HTTPD apache2 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: apache2 Source-Version: 2.2.3-4+etch4 We believe that the bug you reported is fixed in the latest version of apache2, which is due to be installed in the Debian FTP archive: apache2-doc_2.2.3-4+etch4_all.deb to pool/main/a/apache2/apache2-doc_2.2.3-4+etch4_all.deb apache2-mpm-event_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-mpm-event_2.2.3-4+etch4_i386.deb apache2-mpm-perchild_2.2.3-4+etch4_all.deb to pool/main/a/apache2/apache2-mpm-perchild_2.2.3-4+etch4_all.deb apache2-mpm-prefork_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-mpm-prefork_2.2.3-4+etch4_i386.deb apache2-mpm-worker_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-mpm-worker_2.2.3-4+etch4_i386.deb apache2-prefork-dev_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-prefork-dev_2.2.3-4+etch4_i386.deb apache2-src_2.2.3-4+etch4_all.deb to pool/main/a/apache2/apache2-src_2.2.3-4+etch4_all.deb apache2-threaded-dev_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-threaded-dev_2.2.3-4+etch4_i386.deb apache2-utils_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2-utils_2.2.3-4+etch4_i386.deb apache2.2-common_2.2.3-4+etch4_i386.deb to pool/main/a/apache2/apache2.2-common_2.2.3-4+etch4_i386.deb apache2_2.2.3-4+etch4.diff.gz to pool/main/a/apache2/apache2_2.2.3-4+etch4.diff.gz apache2_2.2.3-4+etch4.dsc to pool/main/a/apache2/apache2_2.2.3-4+etch4.dsc apache2_2.2.3-4+etch4_all.deb to pool/main/a/apache2/apache2_2.2.3-4+etch4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please
Bug#421557: marked as done (apache2: increasing memory usage)
Your message dated Wed, 16 Jan 2008 23:05:44 +0100 with message-id [EMAIL PROTECTED] and subject line apache2: increasing memory usage has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: apache2 Version: 2.2.3-4 Severity: normal Apache2's memory usage on a low traffic server keeps on increasing until it brings the whole server the down. Starts with: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 23865 0.1 1.6 23076 8448 ?Ss 04:44 0:00 /usr/sbin/apache2 -k start www-data 23870 0.5 3.4 33052 17532 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23871 0.5 3.5 33040 17916 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23872 0.0 1.3 23476 6860 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23873 0.0 0.8 23076 4072 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23874 0.0 0.8 23076 4084 ?S04:44 0:00 /usr/sbin/apache2 -k start www-data 23877 0.0 0.8 23076 4072 ?S04:44 0:00 /usr/sbin/apache2 -k start A bit later: USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1290 0.0 0.7 23076 3900 ?Ss Apr29 0:00 /usr/sbin/apache2 -k start www-data 1764 0.2 8.5 183828 43596 ?SApr29 3:45 /usr/sbin/apache2 -k start www-data 11452 0.1 9.7 104596 49512 ?SApr29 1:42 /usr/sbin/apache2 -k start www-data 11453 0.2 9.2 106980 47184 ?SApr29 2:06 /usr/sbin/apache2 -k start www-data 11462 0.2 9.4 106444 48056 ?SApr29 1:56 /usr/sbin/apache2 -k start www-data 18776 0.0 5.4 42888 27500 ?SApr29 0:18 /usr/sbin/apache2 -k start www-data 18777 0.1 6.6 49260 33920 ?SApr29 0:24 /usr/sbin/apache2 -k start www-data 18778 0.0 6.1 46496 31116 ?SApr29 0:17 /usr/sbin/apache2 -k start www-data 18779 0.1 6.1 46780 31148 ?SApr29 0:31 /usr/sbin/apache2 -k start www-data 18781 0.0 6.1 46968 31532 ?SApr29 0:21 /usr/sbin/apache2 -k start www-data 18782 0.1 5.7 44612 29160 ?SApr29 0:21 /usr/sbin/apache2 -k start The installation is quite standard, with modules php5, psql auth, and webdav enabled. Cheers, Chris. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.20-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages apache2 depends on: ii apache2-mpm-prefork 2.2.3-4Traditional model for Apache HTTPD apache2 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- version: 2.2.6-3 The patch to reduce the memory usage seems to have fixed this problem. Feel free to reopen the bug or file a new report if the problem appears again. ---End Message---
