From nobody@hyperreal.com Tue Mar 25 10:16:54 1997 Received: by taz.hyperreal.com (8.8.4/V2.0) id KAA12347; Tue, 25 Mar 1997 10:16:54 -0800 (PST) Message-Id: <199703251816.KAA12347@taz.hyperreal.com> Date: Tue, 25 Mar 1997 10:16:54 -0800 (PST) From: Pierre Tremblay Reply-To: trep@cim.mcgill.ca To: apbugs@hyperreal.com Subject: http stops responding for approx 15 minutes then ressucitates X-Send-Pr-Version: 3.2 >Number: 256 >Category: os-bsdi >Synopsis: http stops responding for approx 15 minutes then ressucitates >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Mar 25 10:20:01 1997 >Last-Modified: Sat Apr 19 15:30:16 PDT 1997 >Originator: trep@cim.mcgill.ca >Organization: >Release: 1.2b7 >Environment: problem present on both BSD/OS 2.1 w/all available patches and BSD/OS 3.0, so we don't think it's a FIN_WAIT_2 problem. >Description: Apache apparently stops responding to HTTP requests on all configured Listen ports. Usually, after 15 minutes or so (but sometimes more), it comes back to life and works normally. Nothing abnormal in the log files. >How-To-Repeat: I have a cron job that checks Apache using a perl script that runs wget on the status page. I can provide you with detailed information gathered from the script when wget returns with a timeout (180 seconds): netstat -an, ps -aux, the last Apache status page that was fetched before it stopped responding, or anything else you might suggest. Apache is also SIGHUP'ed by this script after wget returns with a timeout error, and that's successful to get it to work again. The web server address is http://w3.cedep.net/. The locations server-status and server-info are both enabled. >Fix: Unfortunately, no. Just in case, we will recompile with -DNO_LINGCLOSE. %0 >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: dgaudet State-Changed-When: Sat Apr 19 15:30:16 PDT 1997 State-Changed-Why: Superceded by PR#361. >Unformatted: