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:
http://issues.apache.org/bugzilla/show_bug.cgi?id=44402
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.
*lol*
Contradictory information is more of a problem.
I do my best.
Cheers,
Markus Meyer
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
