httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Meyer <>
Subject Re: [users@httpd] Tons of Segfaults in Apache-Prefork 2.2.4
Date Thu, 17 Apr 2008 16:16:08 GMT
Nick Kew schrieb:
> On Thu, 17 Apr 2008 12:13:04 +0200

> Hmmm?  Your subject line says prefork.  With prefork, there are
> no threads.  Anyway, no matter.

Stupid me. This happens when having developers crying in your ear all 
the time ;)

> You should get cores from a segfault.  Have you enabled them?
> (See Coredumpdirectory, and check limitations imposed by your
> operating system and shell).

I enabled CoreDumpDirectory in httpd.conf, made a "ulimit -c unlimited" 
and started Apache. When I had a segfault there was no corefile in the 
specified directory and Apache was still running. Only the forked 
process was gone and a new was spawned. After two days or sometimes a 
week Apache gets really slow and can handle only a fourth or less of 
it's usual traffic.

> We recently (for 2.2.9) fixed a bug that fits that description:
> But that's not relevant to prefork.

Currently the page is not reachable.

> Um, sounds like a problem in the network, below the level of apache.

I'm looking into this too.

> PHP is always a prime suspect for this kind of problem.
> If you're using mod_php, make sure you really are running prefork,
> as PHP+threads is a classic recipe for random segfaults.


> Contradictory information is more of a problem.

I do my best.


	Markus Meyer

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message