I agree that disabling threads is covering up a problem, but I suspect
that the problem is in glibc and not in Apache.
Some rather lame debug suggestions:
1) make sure you have the latest glibc... maybe the problem got fixed
Upgrading to the latest glibc does not seem to help.
2) make
From: Adam Sussman [mailto:[EMAIL PROTECTED]]
Sent: 12 February 2002 03:36
I agree that disabling threads is covering up a problem, but I suspect
that the problem is in glibc and not in Apache.
Some rather lame debug suggestions:
1) make sure you have the latest glibc... maybe
Are you using APR HEAD? We fixed a bug in pools, which was basically
writing too much in too little space.
Yes. We are using HEAD on APR, APR-UTIL and httpd-2.0.
-adam
--
I believe in Kadath in the cold waste, and Ultima Thule. But you
cannot prove to me that Harvard
On Tue, Feb 05, 2002 at 10:45:07PM -0500, Jeff Trawick wrote:
Adam Sussman [EMAIL PROTECTED] writes:
I'm seeing a lot of error messages like this in my error log under load with
lots of children (1300 or so):
...
#0 pthread_sighandler (signo=11, ctx=
{gs = 0, __gsh = 0, fs =
Adam Sussman [EMAIL PROTECTED] writes:
make distclean
./configure --disable-threads old-parameters
make make install
That fixed the problem. So, is this the right solution? Should configure always
assume --disable-threads when it sees --with-mpm=prefork?
I don't believe
I'm seeing a lot of error messages like this in my error log under load with
lots of children (1300 or so):
[Tue Feb 05 12:52:17 2002] [notice] child pid 32299 exit signal Segmentation fault
(11), possible coredump in /tmp
[Tue Feb 05 12:52:17 2002] [notice] child pid 32298 exit signal
