Bug 42667 - mod_proxy_balancer not reporting when workers are re-activated
Summary: mod_proxy_balancer not reporting when workers are re-activated
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy_balancer (show other bugs)
Version: 2.2.3
Hardware: Other Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-14 14:04 UTC by Tom Haddon
Modified: 2007-06-14 14:04 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Haddon 2007-06-14 14:04:03 UTC
I see the following messages in the error log for a specific site that's
configured to use mod_proxy_balancer:

[Thu Jun 14 09:00:06 2007] [error] (111)Connection refused: proxy: HTTP: attempt
to connect to xx.xx.xx.xx:xxx (xx.xx.xx.xx) failed
[Thu Jun 14 09:00:06 2007] [error] ap_proxy_connect_backend disabling worker for
(xx.xx.xx.xx)

However, by checking the application log files, I can see that traffic is being
forwared to this application instance from the apache server running
mod_proxy_balancer. Shouldn't this be reporting somewhere that the worker has
been re-activated?