You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modproxy-dev@apache.org by "Victor J. Orlikowski" <v....@gte.net> on 2001/04/04 11:43:48 UTC
Proxy and cor dump in the filter code...
So, the proxy has a new breakage now. One I need a little help with.
It serves one proxy request, then horks on subsequent requests, with
each subsequent child trying to serve the proxy request dropping core.
The following is the backtrace; I'm still not quite up to snuff enough
on the filter code to figure this one out (that, and the fact that I'd
like a *little* sleep tonight.... :)
#0 0x808e265 in ap_pass_brigade (next=0x2f6f6964, bb=0x8125e6c)
at util_filter.c:240
#1 0x807773e in ap_proxy_http_handler (r=0x8127f7c,
url=0x8125f24 "//foundation/contact.html", proxyname=0x0,
proxyport=0)
at proxy_http.c:558
#2 0x807450b in proxy_handler (r=0x8127f7c) at mod_proxy.c:412
#3 0x808169e in ap_run_handler (r=0x8127f7c) at config.c:132
#4 0x8081d3b in ap_invoke_handler (r=0x8127f7c) at config.c:291
#5 0x8067705 in process_request_internal (r=0x8127f7c) at
http_request.c:355
#6 0x806782f in ap_process_request (r=0x8127f7c) at
http_request.c:419
#7 0x80636ca in ap_process_http_connection (c=0x8125c04) at
http_core.c:280
#8 0x808cd3e in ap_run_process_connection (c=0x8125c04) at
connection.c:82
#9 0x808cf3c in ap_process_connection (c=0x8125c04) at
connection.c:216
#10 0x80800c8 in child_main (child_num_arg=3) at prefork.c:807
#11 0x808020d in make_child (s=0x80e77cc, slot=3) at prefork.c:880
#12 0x8080295 in startup_children (number_to_start=2) at prefork.c:903
#13 0x8080718 in ap_mpm_run (_pconf=0x80e6a54, plog=0x8114bc4,
s=0x80e77cc)
at prefork.c:1111
#14 0x80860ec in main (argc=1, argv=0xbffff724) at main.c:423
Victor
--
Victor J. Orlikowski
======================
v.j.orlikowski@gte.net
orlikowski@apache.org
vjo@us.ibm.com
Re: Proxy and cor dump in the filter code...
Posted by Graham Leggett <mi...@sharp.fm>.
"Victor J. Orlikowski" wrote:
> So, the proxy has a new breakage now. One I need a little help with.
> It serves one proxy request, then horks on subsequent requests, with
> each subsequent child trying to serve the proxy request dropping core.
> The following is the backtrace; I'm still not quite up to snuff enough
> on the filter code to figure this one out (that, and the fact that I'd
> like a *little* sleep tonight.... :)
Need sleep too...
So far the proxy has been working for me - though we might not be
running the same revision of Apache though. What request were you using
to generate this problem?
Regards,
Graham
--
-----------------------------------------
minfrin@sharp.fm "There's a moon
over Bourbon Street
tonight..."