Your message dated Thu, 21 Dec 2006 08:29:52 -0800 with message-id <[EMAIL PROTECTED]> and subject line [php-maint] Bug#402764: libapache2-mod-php5: php processes loop and eat all cpu and resources 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)
--- Begin Message ---Package: libapache2-mod-php5 Version: 5.1.6-5 Severity: important Hello, I run a webserver with some PHP sites and I'm stuck with PHP version 5.1.6. I'm unable to upgrade to version 5.2.0 because suddendly apache processes begin to loop using 100% cpu time and after the while the whole system becomes unresponsive and I need to shutdown apache2 to gain control. I tried to attach to a process with strace and this is what I get: [...] lstat("/var", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 lstat("/var/home", {st_mode=S_IFDIR|0755, st_size=85, ...}) = 0 lstat("/var/home/web2", {st_mode=S_IFDIR|S_ISUID|S_ISGID|0775, st_size=52, ...}) = 0 lstat("/var/home/web2/lc", {st_mode=S_IFDIR|S_ISGID|0775, st_size=95, ...}) = 0 lstat("/var/home/web2/lc/www", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 lstat("/var/home/web2/lc/www/site", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 lstat("/var", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 lstat("/var/home", {st_mode=S_IFDIR|0755, st_size=85, ...}) = 0 lstat("/var/home/web2", {st_mode=S_IFDIR|S_ISUID|S_ISGID|0775, st_size=52, ...}) = 0 lstat("/var/home/web2/lc", {st_mode=S_IFDIR|S_ISGID|0775, st_size=95, ...}) = 0 lstat("/var/home/web2/lc/www", {st_mode=S_IFDIR|0750, st_size=4096, ...}) = 0 lstat("/var/home/web2/lc/www/site", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 [...] over and over and over. The web site on that directory is a standard XOOPS site, and it worked fine for all the others PHP versions since Sarge released. Any hints? -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages libapache2-mod-php5 depends on: ii apache2- 2.2.3-3.1 Traditional model for Apache HTTPD ii apache2. 2.2.3-3.1 Next generation, scalable, extenda ii libbz2-1 1.0.3-6 high-quality block-sorting file co ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libcomer 1.39+1.40-WIP-2006.11.14+dfsg-1 common error description library ii libdb4.4 4.4.20-8 Berkeley v4.4 Database Libraries [ ii libkrb53 1.4.4-4 MIT Kerberos runtime libraries ii libmagic 4.17-4 File type determination library us ii libpcre3 6.7-1 Perl 5 Compatible Regular Expressi ii libssl0. 0.9.8c-4 SSL shared libraries ii libxml2 2.6.27.dfsg-1 GNOME XML library ii mime-sup 3.39-1 MIME files 'mime.types' & 'mailcap ii php5-com 5.1.6-5 Common files for packages built fr ii ucf 2.0017 Update Configuration File: preserv ii zlib1g 1:1.2.3-13 compression library - runtime libapache2-mod-php5 recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 5.2.0-8 hey alessandro, On Thu, 2006-12-21 at 16:48 +0100, Alessandro Polverini wrote: > Hello Sean, and thanks for the info. > > I upgraded to apache2-mpm-prefork 2.2.3-3.2 and PHP 5.2.0-8 since 4 ours > and the bad behaviour has not yet happened... > That's great, I hope the problem is solved with the latest release. that's great to hear, let's hope it stays that way! i am optomistically going to close the bug then, and if the problem resurfaces we can re-open it at a later time. sean
signature.asc
Description: This is a digitally signed message part
--- End Message ---
