Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-12-02 Thread Joe Orton
On Mon, Dec 01, 2003 at 07:52:03AM -0500, Jeff Trawick wrote: FWIW, it segfaults on a jsp request... I suppose that this is handled by a third party module such as mod_jk? See the final snippet: [pid 32119] read(11, GET /messaging/businessObject.js..., 4096) = 775 [pid 32119]

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-12-01 Thread Jeff Trawick
FWIW, it segfaults on a jsp request... I suppose that this is handled by a third party module such as mod_jk? See the final snippet: [pid 32119] read(11, GET /messaging/businessObject.js..., 4096) = 775 [pid 32119] rt_sigaction(SIGUSR1, {SIG_IGN}, {0x4002127c, [], SA_INTERRUPT|0x400}, 8) =

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-12-01 Thread Jeff Trawick
Jeff Trawick wrote: FWIW, it segfaults on a jsp request... I suppose that this is handled by a third party module such as mod_jk? See the final snippet: I was reminded by a little bird that you had mentioned in your original message that you were using the WebLogic plug-in. Maybe some hints

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-12-01 Thread mattyml
On Mon, 1 Dec 2003, Jeff Trawick wrote: FWIW, it segfaults on a jsp request... I suppose that this is handled by a third party module such as mod_jk? See the final snippet: We are using the BEA weblogic plugin to broker *.jsp to our application server. We are using the latest QE'ed build of

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-12-01 Thread mattyml
On Mon, 1 Dec 2003, Jeff Trawick wrote: Jeff Trawick wrote: FWIW, it segfaults on a jsp request... I suppose that this is handled by a third party module such as mod_jk? See the final snippet: I was reminded by a little bird that you had mentioned in your original message that you were

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-11-30 Thread Justin Erenkrantz
--On Saturday, November 29, 2003 10:15 PM -0800 Blair Zajac [EMAIL PROTECTED] wrote: Won't doing something like this work on Linux? ... There's a similar call to prctl(PR_SET_DUMPABLE, 1) in the http 2.0 tree. From talking with Jeff at AC, it sounded like recent versions of the Linux kernel

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-11-29 Thread Blair Zajac
Won't doing something like this work on Linux? --- src/main/http_main.c.0 2002-09-27 10:40:24.0 -0700 +++ src/main/http_main.c2003-06-26 17:11:35.0 -0700 @@ -123,6 +123,7 @@ #ifdef HAVE_BSTRING_H #include bstring.h /* for IRIX, FD_SET calls bzero() */

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-11-28 Thread Justin Erenkrantz
--On Thursday, November 27, 2003 11:27 PM -0500 [EMAIL PROTECTED] wrote: That is a good idea, but there has to be a way to debug things in their current state. Since this is the configuration that causes Apache to No, there's not. It's a problem with Linux not httpd. SEGFAULT, I would like to

Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-11-27 Thread mattyml
Howdy, We are running Apache 1.3.28 (with auth_ldap weblogic plugin) on Redhat Linux 7.3 (latest kernel and glibc RPMs are installed), and for some reason, Apache keeps SEGFAULT'ing every 4 - 5 days. When apache SEGFAULTS, it doesn't produce a core file, and spits out the following items in our

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-11-27 Thread Sander Temme
some reason, Apache keeps SEGFAULT'ing every 4 - 5 days. When apache SEGFAULTS, it doesn't produce a core file, and spits out the following items in our error_log: Did you set your ulimit -S -c to a value other than 0? You need to do that in the shell you start Apache from, before you start

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-11-27 Thread mattyml
On Thu, 27 Nov 2003, Sander Temme wrote: some reason, Apache keeps SEGFAULT'ing every 4 - 5 days. When apache SEGFAULTS, it doesn't produce a core file, and spits out the following items in our error_log: Did you set your ulimit -S -c to a value other than 0? You need to do that I sure

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-11-27 Thread Sander Temme
some reason, Apache keeps SEGFAULT'ing every 4 - 5 days. When apache SEGFAULTS, it doesn't produce a core file, and spits out the following items in our error_log: Did you set your ulimit -S -c to a value other than 0? You need to do that I sure did. I read somewhere that the Linux 2.4

Re: Apache 1.3.28 SEGFAULTS and doesn't produce a core file

2003-11-27 Thread mattyml
On Thu, 27 Nov 2003, Sander Temme wrote: some reason, Apache keeps SEGFAULT'ing every 4 - 5 days. When apache SEGFAULTS, it doesn't produce a core file, and spits out the following items in our error_log: Did you set your ulimit -S -c to a value other than 0? You need to do that I