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/23 16:50:45 UTC
mod_mbox cores
I've had to turn off core dumps from httpd on ajax, because they were
quickly filling up our /tmp directory.
Below is another backtrace that appears a little different from the
first. (I don't believe the module on ajax has been upgraded with the
last fix either.)
Joshua.
#0 mbox_cache_get_count (mli=0x60000000002139c0, count=0x60000fffffffaad0,
path=0x60000000002143d8 "200210.mbox") at mbox_cache.c:247
#1 0x200000000100e230 in show_index_file_info (r=0x6000000000208780,
mli=0x60000000002139c0, path=0x60000000002143d8 "200210.mbox")
at mod_mbox_index.c:84
#2 0x200000000100e880 in generate_mbox_index (r=0x6000000000208780)
at mod_mbox_index.c:187
#3 0x40000000000358f0 in ap_run_handler (r=0x6000000000208780) at
config.c:153
#4 0x40000000000368d0 in ap_invoke_handler (r=0x6000000000208780)
at config.c:317
#5 0x400000000002f460 in ap_process_request (r=0x6000000000208780)
at http_request.c:226
#6 0x40000000000249d0 in ap_process_http_connection (c=0x60000000001d9740)
at http_core.c:233
#7 0x400000000004d1b0 in ap_run_process_connection (c=0x60000000001d9740)
at connection.c:43
#8 0x4000000000032270 in child_main (child_num_arg=23984) at prefork.c:610
#9 0x4000000000032540 in make_child (s=0x6000000000083c20, slot=571)
at prefork.c:704
#10 0x4000000000032ae0 in perform_idle_server_maintenance (p=0x20)
at prefork.c:839
#11 0x4000000000033920 in ap_mpm_run (_pconf=0x0, plog=0x6000000000040288,
s=0x0) at prefork.c:863
Re: mod_mbox cores
Posted by Joshua Slive <jo...@slive.ca>.
Justin Erenkrantz wrote:
> --On August 23, 2005 10:50:45 AM -0400 Joshua Slive <jo...@slive.ca>
> wrote:
>
>> I've had to turn off core dumps from httpd on ajax, because they were
>> quickly filling up our /tmp directory.
>>
>> Below is another backtrace that appears a little different from the
>> first. (I don't believe the module on ajax has been upgraded with the
>> last fix either.)
>
> I think our messages may be crossing. =)
>
> I think these should be resolved now and deployed to ajax. If not,
> please let me know. Thanks. -- justin
Still got segfaults. I reenabled core dumps and directed them at
ajax:/raid1/httpd-cores, where we should have enough space. A backtrace
is also attached below.
Joshua.
#0 mbox_cache_get_count (mli=0x600000000031a220, count=0x60000fffffffa5d0,
path=0x600000000031ac88 "200506.mbox") at mbox_cache.c:247
#1 0x200000000100e250 in show_index_file_info (r=0x6000000000263aa0,
mli=0x600000000031a220, path=0x600000000031ac88 "200506.mbox")
at mod_mbox_index.c:84
#2 0x200000000100e8a0 in generate_mbox_index (r=0x6000000000263aa0)
at mod_mbox_index.c:187
#3 0x40000000000358f0 in ap_run_handler (r=0x6000000000263aa0) at
config.c:153
#4 0x40000000000368d0 in ap_invoke_handler (r=0x6000000000263aa0)
at config.c:317
#5 0x400000000002f460 in ap_process_request (r=0x6000000000263aa0)
at http_request.c:226
#6 0x40000000000249d0 in ap_process_http_connection (c=0x60000000001d9320)
at http_core.c:233
#7 0x400000000004d1b0 in ap_run_process_connection (c=0x60000000001d9320)
at connection.c:43
#8 0x4000000000032270 in child_main (child_num_arg=23984) at prefork.c:610
Re: mod_mbox cores
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On August 23, 2005 10:50:45 AM -0400 Joshua Slive <jo...@slive.ca> wrote:
> I've had to turn off core dumps from httpd on ajax, because they were
> quickly filling up our /tmp directory.
>
> Below is another backtrace that appears a little different from the
> first. (I don't believe the module on ajax has been upgraded with the
> last fix either.)
I think our messages may be crossing. =)
I think these should be resolved now and deployed to ajax. If not, please
let me know. Thanks. -- justin