https://bz.apache.org/bugzilla/show_bug.cgi?id=63273
Bug ID: 63273
Summary: Proxy error doesnot enable the worker even retry
property is enabled.
Product: Apache httpd-2
Version: 2.4.18
Hardware: Other
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: mod_proxy
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
We have setup reverse proxy on frontend servers which connect to backend
servers throught load balancer.
Apache reverse proxy configuration :
ProxyPass http://<load-balancer-DNS>/context/ retry=0 timeout=30
When we do load test, worker for backend connection fails and never get
connected for that backend. Although `retry=0` is specified.
Apache Error log :
[Wed Mar 20 12:23:26.292232 2019] [proxy:trace2] [pid 36176:tid
140617447184128] proxy_util.c(2765): HTTP: fam 2 socket created to connect to
<LOAD-BALANACER-DNS>
[Wed Mar 20 12:23:56.322423 2019] [proxy:error] [pid 36176:tid 140617447184128]
(70007)The timeout specified has expired: AH00957: HTTP: attempt to connect to
10.19.134.64:80 (<LOAD-BALANACER-DNS>) failed
[Wed Mar 20 12:23:56.322496 2019] [proxy:error] [pid 36176:tid 140617447184128]
AH00959: ap_proxy_connect_backend disabling worker for (<LOAD-BALANACER-DNS>)
for 0s
[Wed Mar 20 12:23:56.322509 2019] [proxy:debug] [pid 36176:tid 140617447184128]
proxy_util.c(2175): AH00943: HTTP: has released connection for
(<LOAD-BALANACER-DNS>)
[Wed Mar 20 12:25:57.590705 2019] [proxy:trace2] [pid 36178:tid
140617304508160] proxy_util.c(1966): [client 14.142.125.100:42564] http: found
worker http://<LOAD-BALANACER-DNS>/<API-CONTEXT>/ for
http://<LOAD-BALANACER-DNS>/<API-ENDPOINT>, referer:
https://<APPLICATION-ENDPOINT>/
[Wed Mar 20 12:25:57.590740 2019] [proxy:debug] [pid 36178:tid 140617304508160]
mod_proxy.c(1160): [client 14.142.125.100:42564] AH01143: Running scheme http
handler (attempt 0), referer: https://<APPLICATION-ENDPOINT>/
[Wed Mar 20 12:25:57.590748 2019] [proxy:debug] [pid 36178:tid 140617304508160]
proxy_util.c(1904): AH00932: HTTP: worker for (<LOAD-BALANACER-DNS>) has been
marked for retry
[Wed Mar 20 12:25:57.590767 2019] [proxy:debug] [pid 36178:tid 140617304508160]
proxy_util.c(2160): AH00942: HTTP: has acquired connection for
(<LOAD-BALANACER-DNS>)
[Wed Mar 20 12:25:57.590772 2019] [proxy:debug] [pid 36178:tid 140617304508160]
proxy_util.c(2213): [client 14.142.125.100:42564] AH00944: connecting
http://<LOAD-BALANACER-DNS>/<API-ENDPOINT> to <LOAD-BALANACER-DNS>:80, referer:
https://<APPLICATION-ENDPOINT>/
[Wed Mar 20 12:25:57.590779 2019] [proxy:debug] [pid 36178:tid 140617304508160]
proxy_util.c(2422): [client 14.142.125.100:42564] AH00947: connected
/<API-ENDPOINT> to <LOAD-BALANACER-DNS>:80, referer:
https://<APPLICATION-ENDPOINT>/
[Wed Mar 20 12:25:57.590798 2019] [proxy:trace2] [pid 36178:tid
140617304508160] proxy_util.c(2765): HTTP: fam 2 socket created to connect to
<LOAD-BALANACER-DNS>
[Wed Mar 20 12:26:00.588182 2019] [proxy:debug] [pid 36178:tid 140617304508160]
proxy_util.c(2790): (113)No route to host: AH00957: HTTP: attempt to connect to
10.19.136.229:80 (<LOAD-BALANACER-DNS>) failed
--------------------------------------------------------------------------
Restarting apache server, then workers starts reconnecting to backend.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
