This is almost certainly because you've run out of file descriptors. However it'd be nice to know where we're dumping core without exiting gracefully. If you could provide a stack trace that'd be great.
Dean On Wed, 12 Mar 1997, Bradley White wrote: > > The contract type is `' with a response time of 3 business hours. > A first analysis should be sent before: Thu Mar 13 11:00:00 PST 1997 > > > >Number: 231 > >Category: os-bsdi > >Synopsis: child process dump core > >Confidential: no > >Severity: critical > >Priority: medium > >Responsible: apache (Apache HTTP Project) > >State: open > >Class: sw-bug > >Submitter-Id: apache > >Arrival-Date: Wed Mar 12 20:50:00 1997 > >Originator: [EMAIL PROTECTED] > >Organization: > apache > >Release: 1.2b7 > >Environment: > BSDI 2.1 Fully Patched and BSDI 3.0 dist. gcc is the compiler > >Description: > When configuring Apache for more than 125 virtual hosts that use one single > ip address http1.1 style, the child process start dumping core. It's > interesting that the parent process does not dump core. The syptoms of this > are > are web pages that should be working, coming up as either connection reset by > peer or document contains no data. A check of the error_log while this is > going > on shows the child process giving out a segment violation. > >How-To-Repeat: > Configure a bsd/os server with 126 or more virtual web servers http1.1 style. > > We are unable to test with any other OS at this time. > >Fix: > N > >Audit-Trail: > >Unformatted: > > >
