*BSD News Article 79212


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!psgrain!charnel.ecst.csuchico.edu!newshub.csu.net!csulb.edu!news.sgi.com!enews.sgi.com!www.nntp.primenet.com!nntp.primenet.com!howland.erols.net!vixen.cso.uiuc.edu!sdd.hp.com!col.hp.com!jolt.pagesat.net!pagesat.net!news.digicity.net!usenet
From: Damien Thorn <damien@digicity.net>
Newsgroups: comp.infosystems.www.servers.unix,comp.unix.bsd.freebsd.misc
Subject: Re: Apache 1.1.1 Dumping Core
Date: Wed, 25 Sep 1996 15:25:11 -0700
Organization: Digital City Communications, Inc.
Lines: 26
Message-ID: <3249B147.3A06@digicity.net>
References: <dlt-2309960726280001@news.csun.edu> <fred-2509960127580001@calcium.shocking.com>
NNTP-Posting-Host: sidewinder.digicity.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.01 (Win16; I)
Xref: euryale.cc.adfa.oz.au comp.infosystems.www.servers.unix:19724 comp.unix.bsd.freebsd.misc:28028

Fred Condo wrote:
> 
> In article <dlt-2309960726280001@news.csun.edu>, dlt@csun.edu (David
> Thompson) 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.

Hmmm.  This was disturbing to read, however we currently serve about 25
virtual domains and a single FreeBSD (2.1.0R) box (Pentium 133, 64 Meg,
couple of SCSI drives) without having encountered this problem.  The
server has pumped about 300-400k of continuous traffic for days at a time
and been okay.

Is it possible this problem is related to something else happening on
the system?