You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Joshua Slive <jo...@slive.ca> on 2005/08/15 22:01:46 UTC

mod_mbox seg faulting on ajax

[What is the active mod_mbox devel list?  Trying dev@httpd...]

As the subject says, mod_mbox has seg faulted about 50 times so far 
today on ajax.  Some core files in ajax:/tmp (after hacking apachectl to 
adjust the ulimits).

Here's a backtrace
#0  find_thread (r=0x600000000021b870,
     msgID=0x600000000021ce60 
"<EC...@blr02.bynum.com>", 
        c=0x0) at mod_mbox_file.c:155
#1  0x200000000100a920 in find_next_thread (r=0x600000000021b870,
     msgID=0x600000000021ce60 
"<EC...@blr02.bynum.com>", 
        c=0x0) at mod_mbox_file.c:216
#2  0x200000000100ad20 in fetch_relative_message (r=0x600000000021b870,
     f=0x600000000021ce60, flags=3) at mod_mbox_file.c:298
#3  0x200000000100da90 in mbox_file_handler (r=0x600000000021b870)
     at mod_mbox_file.c:945
#4  0x40000000000358f0 in ap_run_handler (r=0x600000000021b870) at 
config.c:153
#5  0x40000000000368d0 in ap_invoke_handler (r=0x600000000021b870) at 
config.c:317
#6  0x400000000002f460 in ap_process_request (r=0x600000000021b870)
     at http_request.c:226
#7  0x40000000000249d0 in ap_process_http_connection (c=0x60000000001d9320)
     at http_core.c:233
#8  0x400000000004d1b0 in ap_run_process_connection (c=0x60000000001d9320)
     at connection.c:43
#9  0x4000000000032270 in child_main (child_num_arg=23984) at prefork.c:610
#10 0x4000000000032540 in make_child (s=0x6000000000045730, slot=60) at 
prefork.c:704
#11 0x40000000000327c0 in startup_children (number_to_start=89) at 
prefork.c:715
#12 0x4000000000033950 in ap_mpm_run (_pconf=0x6000000000008c4c,
     plog=0x6000000000040288, s=0x0) at prefork.c:941
#13 0x4000000000041610 in main (argc=5, argv=0x60000fffffffb0d8) at 
main.c:618

Re: mod_mbox seg faulting on ajax

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On August 17, 2005 12:09:39 PM -0700 Justin Erenkrantz 
<ju...@erenkrantz.com> wrote:

> Sure.  I'll hopefully get around to this in the next day or so.  -- justin

I've now updated ajax to trunk.  -- justin

Re: mod_mbox seg faulting on ajax

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On August 17, 2005 1:10:22 PM -0400 Joshua Slive <jo...@slive.ca> wrote:

> Justin... Would it be possible for you to try this out on ajax.  I could
> try to do it myself, but I would need to replicate your setup.
>
> I don't think the core dumps are creating any real problem, but I hate to
> see them on our main server.

Sure.  I'll hopefully get around to this in the next day or so.  -- justin

Re: mod_mbox seg faulting on ajax

Posted by Joshua Slive <jo...@slive.ca>.
Paul Querna wrote:
> Joshua Slive wrote:
>> [What is the active mod_mbox devel list?  Trying dev@httpd...]
> 
> dev@httpd is the best list.
> 
>> As the subject says, mod_mbox has seg faulted about 50 times so far
>> today on ajax.  Some core files in ajax:/tmp (after hacking apachectl to
>> adjust the ulimits).
> 
> I think I just fixed this in trunk with r233127, but I didn't have
> enough spare cycles to test/reproduce it.

Justin... Would it be possible for you to try this out on ajax.  I could 
try to do it myself, but I would need to replicate your setup.

I don't think the core dumps are creating any real problem, but I hate 
to see them on our main server.

Joshua.

Re: mod_mbox seg faulting on ajax

Posted by Paul Querna <ch...@force-elite.com>.
Joshua Slive wrote:
> [What is the active mod_mbox devel list?  Trying dev@httpd...]

dev@httpd is the best list.

> As the subject says, mod_mbox has seg faulted about 50 times so far
> today on ajax.  Some core files in ajax:/tmp (after hacking apachectl to
> adjust the ulimits).

I think I just fixed this in trunk with r233127, but I didn't have
enough spare cycles to test/reproduce it.

-Paul