Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:8844 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54845 invoked by uid 1010); 31 Mar 2004 09:48:26 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 54736 invoked from network); 31 Mar 2004 09:48:24 -0000 Received: from unknown (HELO art3mis.com) (217.172.66.234) by pb1.pair.com with SMTP; 31 Mar 2004 09:48:24 -0000 Received: (qmail 18916 invoked from network); 31 Mar 2004 09:48:17 -0000 Received: from unknown (HELO SPAWN) (80.38.117.84) by 10.1.0.18 with SMTP; 31 Mar 2004 09:48:17 -0000 To: Date: Wed, 31 Mar 2004 11:49:20 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C41716.349CD7F0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcQXBXC78Os8NK2qTh2+YmIOgSAj/w== X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on wolverine X-Spam-Status: No, hits=0.5 required=4.0 tests=HTML_40_50,HTML_MESSAGE autolearn=no version=2.63 X-Spam-Level: Subject: Apache 2.0.49 + PHP5.0.0RC1 crashes randomly From: jalonso@art3mis.com ("Juan Alonso") Message-ID: ------=_NextPart_000_0005_01C41716.349CD7F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello, PHP seems to crash randomly with Apache 2.0.49. I made clean installs of both Apache 2.0.48 and 2.0.49 and I recompiled PHP from a clean state both times and there is no problem with 2.0.48. I know this is a pretty useless bug report but I don't know where to look for more details. The application running behind is really complex and pushes PHP in several ways but the apache server seems to die while there is no one using it. If you tell me what kind of details to search for to find the cause of the bug I will be glad to help. This are the only entries in the apache logs that seem to be related to this problem: [Tue Mar 30 23:00:02 2004] [notice] SIGHUP received. Attempting to restart [Tue Mar 30 23:00:02 2004] [notice] seg fault or similar nasty error detected in the parent process As the log says when this bug happens it kills the parent process, not only a kid. With other kind of bugs I got segmentation faults but they didn't killed the main Apache process. System is debian woody and here is PHP config line: ./configure --prefix=/usr/local --with-config-file-path=/usr/local/lib --enable-cli --disable-cgi --with-apxs2=/usr/local/bin/apxs --enable-sockets --with-zlib --without-dom-xslt --with-gd --with-jpeg-dir --with-png-dir --with-zlib-dir --with-ttf --with-freetype --with-zlib-dir --with-pgsql=/usr/local --enable-memory-limit --enable-mbstring --enable-zend-multibyte --without-pear --disable-tokenizer --enable-xml --with-libxml-dir=/usr/local --enable-simplexml --with-libxml-dir=/usr/local --enable-dom --with-libxml-dir=/usr/local --enable-posix --disable-ctype --with-mime-magic Regards ------=_NextPart_000_0005_01C41716.349CD7F0--