Re: Apache Signal 11 (5.3-RELEASE-p3/4)

2005-03-20 Thread Randy Bush
> I have the same problem, started at some point since 5.3-p? > > I thought something is wrong with the particular server, but since > other people report the same issue, I started to doubt that. me too running current with apache+mod_ssl-1.3.33+2.8.22 from the ports tree randy _

Re: Apache Signal 11 (5.3-RELEASE-p3/4)

2005-03-19 Thread Michael C. Shultz
On Saturday 19 March 2005 04:58 am, Vlad wrote: > I have the same problem, started at some point since 5.3-p? > > I thought something is wrong with the particular server, but since > other people report the same issue, I started to doubt that. > > Apache has been built manually, so it has nothing t

Re: Apache Signal 11 (5.3-RELEASE-p3/4)

2005-03-19 Thread Vlad
I have the same problem, started at some point since 5.3-p? I thought something is wrong with the particular server, but since other people report the same issue, I started to doubt that. Apache has been built manually, so it has nothing to do with the port. 1.3.33 Apache + mod_ssl + mod_perl So

Re: Apache Signal 11 (5.3-RELEASE-p3/4)

2005-03-17 Thread Kyle Mott
I took your advice and rebuilt apache with debugging symbols, and came up with this (following http://httpd.apache.org/dev/debugging.html): [EMAIL PROTECTED]:/usr/ports/www/apache13-modssl# gdb httpd (gdb) b ap_process_request Breakpoint 1 at 0x8064944: file http_request.c, line 1311. (gdb) run -X

Re: Apache Signal 11 (5.3-RELEASE-p3/4)

2005-03-17 Thread Michael C. Shultz
On Thursday 17 March 2005 10:28 am, Kyle Mott wrote: > I've already sent this question to freebsd-questions; forgive me if > this is the wrong list. > > This just very recently started to happen (and I haven't upgraded > Apache as of late either, or any other software for that matter). I > keep get

Apache Signal 11 (5.3-RELEASE-p3/4)

2005-03-17 Thread Kyle Mott
I've already sent this question to freebsd-questions; forgive me if this is the wrong list. This just very recently started to happen (and I haven't upgraded Apache as of late either, or any other software for that matter). I keep getting this in my kernel.log on 2 different hosts: Mar 17 09:34