Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 33163 invoked by uid 500); 1 Apr 2003 10:11:50 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 33102 invoked from network); 1 Apr 2003 10:11:49 -0000 Received: from public.ndh.net (HELO public.ndh.com) (195.94.90.21) by daedalus.apache.org with SMTP; 1 Apr 2003 10:11:49 -0000 Received: from PC199 ([195.227.6.99]) by public.ndh.com (8.12.8/8.8.0) with SMTP id h31AC1Vn022610 for ; Tue, 1 Apr 2003 12:12:01 +0200 (MEST) Message-ID: <01ab01c2f837$2d792900$6301e3c3@NDH> From: "Alexander Meis" To: Date: Tue, 1 Apr 2003 12:12:18 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: [users@httpd] Spontaneous POST-Requestvars removal (Apache 1.3.27) Hi... We use Apache 1.3.27 with default configuration and two virtual hosts on an Compaq ProLiant 380 dual system, RedHat 7.3. Using mod_cgi and some perl scripts of an CMS software (Imperia) we are facing spontaneous POST-Variable loss for those Perl/Cgi-Scripts. I wrote a small PHP script which posts data to a CGI-script, and the CGI-script evaluates what parameters were sent. About 7% of all POST requests do not contain data. We allready double-checked our configuration, deactivated nearly all unneccessary modules and deactivated SSL-support. We upgrade all components to the most current releases, but nothing helps. The specialty is, as we have found out, that the behaviour only starts to happen after about 30 minutes of Apache-Usage. We now added a small workaround to restart apache gracefully every 15 minutes. We have no problems so far, but this can't be a permanent solution. We guess there may be some memory-access bug in apache or something like that. On the hardware-side, the RAM should be okay because MySQL runs stable. Are there any things we could try to evaluate? Some debugging-options, so we can track the bug down? Thanks for any hints, Alex Meis --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org