www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Erenkrantz <jerenkra...@ebuilt.com>
Subject Re: os-bsdi/9940: Apache 2.0 crashes
Date Wed, 27 Feb 2002 06:06:01 GMT
On Tue, Feb 26, 2002 at 10:59:10PM -0700, System Administrator a.k.a. The Root of the Problem
wrote:
> On Tue, Feb 26, 2002 at 09:17:59PM -0800, Justin Erenkrantz wrote:
> > On Tue, Feb 26, 2002 at 10:12:00AM -0700, System Administrator a.k.a. The Root of
the Problem wrote:
> > > > Shouldn't you have more than 64 open files available?
> > > > Try "ulimit -n 500"?
> > > > 
> > > > It sounds like we are opening all log files at startup,
> > > > which may or may not be reasonable.  -- justin
> > > > 
> > >  How is that does universally in bash?
> > 
> > You could set this in your .bash_profile.
> > 
> > But just try:
> > 
> > ulimit -n 500
> > apachectl start
> > 
> > See what it does then.  -- justin
> > 
> 
> 
> Bad news, yese apache 2 start BUT the server panics BIG time!!
> 
> kmem_suballoc: bad status return of 1.
> panic(cpu-1): kmem_suballoc
> syncing discs ...
> 
> Not a pretty picture.

I'm afraid I'm out of my depth here.  How did this cause a kernel
panic?  Is there something else going on here?  Could you try
with different ulimit values?  -- justin


Mime
View raw message