https://issues.apache.org/bugzilla/show_bug.cgi?id=53388
Priority: P2
Bug ID: 53388
Assignee: [email protected]
Summary: mod_proxy_balanser generates 503 when proxying to a
balancermember which isn't defined
Severity: normal
Classification: Unclassified
OS: Linux
Reporter: [email protected]
Hardware: PC
Status: NEW
Version: 2.2.22
Component: mod_proxy_balancer
Product: Apache httpd-2
Hi,
Camed across a strange thing today. A customer said his reverse proxied website
was not working over https.
After some troubleshooting I found this:
[Fri Jun 08 08:18:40 2012] [error] proxy: BALANCER: (balancer://idm). All
workers are in error state
[Fri Jun 08 08:19:38 2012] [error] proxy: BALANCER: (balancer://idm). All
workers are in error state
<Proxy balancer://iam>
Order deny,allow
Allow from all
BalancerMember http://xxx.xxx.xx.xx:8080/iam route=worker0
BalancerMember http://xxx.xxx.xx.xx:8080/iam route=worker1
</Proxy>
ProxyPass /iam balancer://idm stickysession=JSESSIONID
ProxyPassReverse /iam balancer://idm
Should be:
ProxyPass /iam balancer://iam stickysession=JSESSIONID
ProxyPassReverse /iam balancer://iam
So it seems like when you write a name of a balancer member which isn't
defined, it's not checked when verifying the config. It starts up with no
errors. But when accessing it, it gererates 503s.
Best regards,
Peter
--
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]
