From owner-freebsd-stable@FreeBSD.ORG Thu Jan 29 09:33:35 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A29116A4CE for ; Thu, 29 Jan 2004 09:33:35 -0800 (PST) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0F1943D45 for ; Thu, 29 Jan 2004 09:33:12 -0800 (PST) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smtp3.sentex.ca (8.12.10/8.12.10) with ESMTP id i0THX9UE072279; Thu, 29 Jan 2004 12:33:09 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net ([192.168.43.27]) by lava.sentex.ca (8.12.9p2/8.12.9) with ESMTP id i0THX9Im007875; Thu, 29 Jan 2004 12:33:09 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.0.1.1.0.20040129115657.05aa05c0@209.112.4.2> X-Sender: mdtpop@209.112.4.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Thu, 29 Jan 2004 12:32:09 -0500 To: Matt King , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <40193A92.8030301@magnetinternet.com> References: <40193A92.8030301@magnetinternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Subject: Re: httpd exiting on signal 11 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2004 17:33:35 -0000 At 11:53 AM 29/01/2004, Matt King wrote: >I built Apache from source (not from ports) and it runs great, except >every once in a while in the dmesg output I get: > >pid 98142 (httpd), uid 65534: exited on signal 11 > >I don't know if it affects performance at all, and I haven't heard anyone >complain, so I've just ignored it. I'm wondering if anyone else has had >this quirk and if they know why it's causing it. > >I know signal 11 is usually a sign of bad memory or buggy hardware, Or buggy software. eg. a cgi script like #include int main(void) { char *t2; char t; t2= (char *) malloc(10); t = t2[40000]; return 0; } will cause the apache process running the script to die with a sig 11. Where you need to be careful of about hardware is in situations where known good programs are aborting randomly with sig 11s. eg. if you are getting random sig 11s when doing a buildworld. That is usually indicative of bad hardware. Take a look through your apache logs to see what is causing the sig 11. It might just be some buggy cgi script. ---Mike