Bug 47706

Summary: (20014)Internal error: proxy: error reading status line from remote server
Product: Apache httpd-2 Reporter: jagusztinl
Component: mod_proxyAssignee: Apache HTTPD Bugs Mailing List <bugs>
Status: RESOLVED LATER    
Severity: normal Keywords: MassUpdate
Priority: P2    
Version: 2.2.11   
Target Milestone: ---   
Hardware: Sun   
OS: Solaris   

Description jagusztinl 2009-08-19 00:25:42 UTC 
We have frequent errors in error.log:
Wed Aug 19 00:22:16 2009] [error] [client 78.92.4.90] (20014)Internal error: proxy: error reading status line from remote server terra2
[Wed Aug 19 00:22:16 2009] [error] [client 78.92.4.90] proxy: Error reading from remote server returned by /aspportal/index.html
[Wed Aug 19 01:22:15 2009] [error] [client 78.92.4.90] (20014)Internal error: proxy: error reading status line from remote server terra2
[Wed Aug 19 01:22:15 2009] [error] [client 78.92.4.90] proxy: Error reading from remote server returned by /aspportal/index.html
[Wed Aug 19 03:22:15 2009] [error] [client 78.92.4.90] (20014)Internal error: proxy: error reading status line from remote server terra2
[Wed Aug 19 03:22:15 2009] [error] [client 78.92.4.90] proxy: Error reading from remote server returned by /aspportal/index.html

What can cause this? The target server is Glassfish v2.1

Config:

<Proxy balancer://asp_cluster>
   ProxySet stickysession=JSESSIONID timeout=10 maxattempts=3

   BalancerMember http://terra1:48080 route=asp_server1  timeout=120   retry=0
   BalancerMember http://terra2:48080 route=asp_server2  timeout=120   retry=0
</Proxy>


Regards.,
LJ
Comment 1 Ruediger Pluem 2009-08-19 12:07:01 UTC 
Is this the error log of your virtual host? If yes please have a look in the global one. It is likely to contain corresponding error message that resolve 20014 to a human readable text.
Comment 2 William A. Rowe Jr. 2018-11-07 21:09:40 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.