*BSD News Article 79757


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!vic.news.telstra.net!act.news.telstra.net!nsw.news.telstra.net!asstdc.scgt.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!solace!news.stealth.net!www.nntp.primenet.com!nntp.primenet.com!cam-news-hub1.bbnplanet.com!news.mathworks.com!newsfeed.internetmci.com!news.sesqui.net!uhura.phoenix.net!usenet
From: Geoff Mohler <gemohler@phoenix.net>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Apache 1.1.1 Dumping Core
Date: Wed, 02 Oct 1996 15:08:51 -0700
Organization: Phoenix Data Net
Lines: 28
Message-ID: <3252E7F3.2781@phoenix.net>
References: <dlt-2309960726280001@news.csun.edu>
		<fred-2509960127580001@calcium.shocking.com> <57zq2e7jvu.fsf@tees.elsevier.co.uk>
NNTP-Posting-Host: sgi.phoenix.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0Gold (X11; I; IRIX 5.3 IP22)

Paul Richards wrote:

> > >I'm seeing a LOT of these messages in my error_log.  Should I be concerned?
> > >
> > >[Mon Sep 23 07:19:24 1996] httpd: caught SIGSEGV, dumping core
> > >[Mon Sep 23 07:19:31 1996] httpd: caught SIGSEGV, dumping core
> > >[Mon Sep 23 07:19:31 1996] httpd: caught SIGSEGV, dumping core
> >
> > Yes! This problem occurs when you have "too many" Virtual Hosts. "Too
> > many" seems to depend on random variables: one FreeBSD machine I know
> > cannot run even a single Virtual Host without dropping SIGSEGV on every
> > hit. Another machine I know can run 7 Virtual Hosts without problems, but
> > adding an 8th causes some, but not all, of the Virtual Hosts to drop a
> > SIGSEGV.

I can confidently assure you, that with my four WWW machines running
Apache
1.1.1, and three of them with 130 virtual servers/hosts each, Ive never
recorded
one single error or warning.

Going past approximately 130 servers is different..proably related to a
open files 
limit being reached *two logs per virtual*.

But again, this is not a problems with Apache as we've ever used it on
2.1.0 or
2.1.5.