Received: (qmail 15714 invoked by uid 2012); 25 Jun 1999 15:24:58 -0000 Message-Id: <19990625152458.15713.qmail@hyperreal.org> Date: 25 Jun 1999 15:24:58 -0000 From: Fabio Lahr Reply-To: flahr@idgsp.idg.com.br To: apbugs@hyperreal.org Subject: kernel panic running 32 or more copies of ApacheBench X-Send-Pr-Version: 3.2 >Number: 4651 >Category: os-other >Synopsis: kernel panic running 32 or more copies of ApacheBench >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Jun 25 08:30:01 PDT 1999 >Last-Modified: Sun Aug 15 02:48:33 PDT 1999 >Originator: flahr@idgsp.idg.com.br >Organization: >Release: Apache 1.3.4 >Environment: Apache 1.3.4 Macintosh Blue G3/400 running MOSXS >Description: xserverfatalbug On Mac OS X When 32 or more copies of ApacheBench (ab) are pointed at a CGI script on a website running on Apache/Mac OS X Server machine, the kernel will panic, usually within 30-60 seconds, forcing a reboot. In the test, c't directed 32 copies of ApacheBench at the "test-cgi" script which is in /Local/Library/WebServer/CGI-Executables/. By default, the script is not executable. You must 'chmod +x test-cgi' for it to work. However, this could probably happen with any script, though tests of that sort were not published. I actually tested this on my Blue G3/400 running MOSXS and did get a kernel panic. I got essentially the same results whether launching the attack from the same machine that the webserver itself is on, or launching the attack from a linux machine on the same network. Incidentally, I ran this same test again a Red Hat Linux 5.1 (2.0.34 kernel) box, which did not experience any problems during the "attack." >How-To-Repeat: http://www.macnn.com/reports/xserverfatalbug.shtml Has info on it >Fix: No but it seems to be related to Apache running on MOSX >Audit-Trail: Category-Changed-From-To: general-os-other Category-Changed-By: fielding Category-Changed-When: Sun Aug 15 02:48:33 PDT 1999 >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]