|Summary:||mod_proxy_balancer not reporting when workers are re-activated|
|Product:||Apache httpd-2||Reporter:||Tom Haddon <tom>|
|Component:||mod_proxy_balancer||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
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?
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:54 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.