We were on 2.0.27-dev for an hour and a half tonight. We very quickly hit MaxClients, which is at 600, because we were getting pounded with requests for xml.apache.org from one client. Once I put him in the penalty box, we were able to handle the workload without a problem.
But we took two seg faults, so I moved us back to 2.0.24. The URL was http://search.apache.org/ . This was a POST request. The dumps are /usr/local/apache2.0.26-debug/corefiles/httpd.core.1 and .2, and they look the same. #0 0x80739be in core_input_filter (f=0x8125364, b=0x81dd7fc, mode=AP_MODE_BLOCKING, readbytes=0xbfbf7660) at core.c:2875 #1 0x806cebd in ap_get_brigade (next=0x8125364, bb=0x81dd7fc, mode=AP_MODE_BLOCKING, readbytes=0xbfbf7660) at util_filter.c:250 #2 0x805e4c7 in ap_get_client_block (r=0x81dd484, buffer=0xbfbf96e8 "keyword=Windows+XP&results=20&what=httpd.apache.org&version=2", bufsiz=8192) at http_protocol.c:1377 #3 0x281b57b8 in cgi_handler (r=0x81dd484) at mod_cgi.c:629 #4 0x8062ff7 in ap_run_handler (r=0x81dd484) at config.c:185 #5 0x806358f in ap_invoke_handler (r=0x81dd484) at config.c:344 #6 0x8060ac5 in ap_internal_redirect (new_uri=0x81dd45c "/index.cgi", r=0x81da03c) at http_request.c:444 #7 0x281ecca5 in handle_dir (r=0x81da03c) at mod_dir.c:194 #8 0x8062ff7 in ap_run_handler (r=0x81da03c) at config.c:185 #9 0x806358f in ap_invoke_handler (r=0x81da03c) at config.c:344 #10 0x8060675 in ap_process_request (r=0x81da03c) at http_request.c:286 #11 0x805c402 in ap_process_http_connection (c=0x8125114) at http_core.c:289 #12 0x806b56f in ap_run_process_connection (c=0x8125114) at connection.c:82 #13 0x806b72d in ap_process_connection (c=0x8125114) at connection.c:219 #14 0x8061bf0 in child_main (child_num_arg=318) at prefork.c:830 #15 0x8061d46 in make_child (s=0x8095974, slot=318) at prefork.c:917 #16 0x8061f99 in perform_idle_server_maintenance (p=0x809500c) at prefork.c:1058 #17 0x806235a in ap_mpm_run (_pconf=0x809500c, plog=0x80ce00c, s=0x8095974)
