Bug 57067 - A proxy worker both standalone and balancer member may not be fully initialized
Summary: A proxy worker both standalone and balancer member may not be fully initialized
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy_balancer (show other bugs)
Version: 2.2-HEAD
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate, PatchAvailable
Depends on:
Blocks:
 
Reported: 2014-10-08 11:58 UTC by Yann Ylavic
Modified: 2018-11-07 21:09 UTC (History)
1 user (show)



Attachments
Force initialization of lb parameters if they are not already (926 bytes, patch)
2014-10-08 11:58 UTC, Yann Ylavic
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Yann Ylavic 2014-10-08 11:58:43 UTC
Created attachment 32092 [details]
Force initialization of lb parameters if they are not already

If a proxy worker is first declared as standalone (<Proxy> or ProxyPass) and then also used as a BalancerMember, PROXY_WORKER_INITIALIZED is set during the first call to ap_proxy_initialize_worker_share(), and hence the second call from init_balancer_members() won't initialize lbset, lbstatus and lbfactor.

The latter parameter is problematic since it is used as divisor with lbmethod bytraffic, causing a crash.

The attached patch fixes it.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:59 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.