Apache Error 20014
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more proxy error reading status line about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask
Apache 20014 Internal Error
Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign
Proxy: Error Reading Status Line From Remote Server
up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top error 20014 with mod_proxy up vote 1 down vote favorite 1 I have strange situation.
Ah00898: Error Reading From Remote Server Returned By
I need to call a program in cgi-bin from within a perl script. When I try to do that with exec($program), I get (20014)Internal error: proxy: error reading status line from remote server proxy: Error reading from remote server returned by ... The long story... I am calling mapserv (http://mapserver.org) as a cgi program from OpenLayers (http://openlayers.org). Ordinarily, my web site is served by Perl Dancer, but the mapserver calls are made directly to http://server/cgi-bin/mapserv from JavaScript. The error reading status line from remote server localhost Dancer web site is served by Starman behind an Apache2 proxy front-end. This is how it looks [browser] -> http://server/app -> [apache2] -> proxy port 5000 -> Starman | | +-> http://server/cgi-bin/mapserv -> [apache2] -> cgi-bin -> mapserv This is what I am trying to accomplish [browser] -> http://server/app -> [apache2] -> proxy port 5000 -> Starman | | mapserv <-- cgi-bin <-- [apache2] <--+ I saw this question re: 20014 error, but that suggested solution didn't help. Any other hints? apache-2.2 mod-proxy share|improve this question asked Nov 8 '11 at 1:33 punkish 13317 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote I'm not sure which version of Apache are you using. I've had a similar issue with Apache 2.2.22, and Apache's documentation suggests the following: proxy-initial-not-pooled If this variable is set no pooled connection will be reused if the client connection is an initial connection. This avoids the "proxy: error reading status line from remote server" error message caused by the race condition that the backend server closed the pooled connection after the connection check by the proxy and before data sent by the proxy reached the backend. It has to be kept in mind that setting this variable downgrades performance, especially with HTTP/1.0 clients. But i'm not sure if that will resolve your issue. share|improve this answer edited Apr 10 '12 at 16:46 voretaq7♦ 68
Forgot Password Login: [x] First Last Prev Next This bug is not in your last search results. Bug48037 - mod_proxy_http does not handle asynchronous keepalive close events correctly Summary: mod_proxy_http does not proxy-initial-not-pooled handle asynchronous keepalive close events correctly Status: NEW Product: Apache httpd-2 Classification: Unclassified Component: connection reset by peer proxy error reading status line from remote server mod_proxy_http Version: 2.0.63 Hardware: PC Linux Importance: P2 normal with 2 votes (vote) TargetMilestone: --- Assigned To: Apache HTTPD Bugs Mailing (70007)the timeout specified has expired: proxy: error reading status line from remote server List URL: Keywords: Depends on: Blocks: Show dependency tree Reported: 2009-10-21 16:35 UTC by John Lightsey Modified: 2016-08-01 03:04 UTC (History) CC List: 4 users (show) helen jd sokann williama_lovaton Attachments server config files http://serverfault.com/questions/328715/error-20014-with-mod-proxy (3.82 KB, application/zip) 2016-01-11 11:30 UTC, Helen Details Server Config files (3.82 KB, application/zip) 2016-01-11 11:32 UTC, Helen Details View All Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description John Lightsey 2009-10-21 16:35:38 UTC Noticed this with Apache 2.0.63, but it looks fairly clear that the same problem exists in 2.2.14. The way proxy_httpd.c https://bz.apache.org/bugzilla/show_bug.cgi?id=48037 is written, if a keepalive connection is closed by the other side in ap_proxy_http_handler() after ap_proxy_http_create_connection() and before a response is received, Apache will consider this to be a connection error and generate a 502 response. This logic is only valid on the first request across the keepalive. According to the HTTP 1.1 spec, proxy_httpd.c must be capable of handling asynchronous close events in the middle of a keepalive session. When it encounters an unexpected close it should attempt to reestablish the connection and resend the request before generating a 502 response. Comment 1 Ruediger Pluem 2012-08-10 06:39:44 UTC Please check a recent 2.2.x / 2.4.x. This should have the problem fixed. Comment 2 William Lovaton 2013-04-13 18:16:43 UTC Sorry, but this problem is still happening. I'm testing httpd 2.2.23 from http://centos.alt.ru/repository/centos/6/x86_64/ repository on a RHEL 6.4 server. I was seeing the same problem from official RHEL packages (httpd-2.2.15-26.el6.x86_64.rpm) and updating to 2.2.23 didn't solve the problem. My configuration is as follows: * Reverse Proxy: RHEL 6.4 with apache 2.2.23 from CentosALT (Worker MPM) * Backend Servers: 2 x RHEL 6.2 with apache 2.2.15-15.el6.x86_64 from RHEL (Prefork MPM, huge in-house PHP 5 web app) I'm using mod proxy balancer to spread the load between the 2 servers with the following c
proxy functionality to pass traffic back and forth. What we error reading started seeing under load was the following: (20014)Internal error: proxy: error reading status line from remote server 127.0.0.1 To fix this I error reading status added these two lines in our locationmatch containers: SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 This appears to have resolved our issue. Tagged on: Apache Error, Apache How-To By RElliott Technologies | May 22, 2013 | Apache, Glassfish | ← Zend 6 - Installation Apache - 417 error → Copyright © 2016 RElliott Technologies | Theme by: Theme Horse | Powered by: WordPress Back to Top