Error Reading Status Line Apache
Contents |
First Last Prev Next This bug is not in your last search results. Bug39499 apache proxy error reading status line from remote server - error reading status line, reverse proxy, broken pipe Summary: error error reading status line from remote server localhost reading status line, reverse proxy, broken pipe Status: RESOLVED DUPLICATE of bug 37770 Product: Apache httpd-2 Classification: ah01102 error reading status line from remote server Unclassified Component: mod_proxy Version: 2.2.2 Hardware: All Linux Importance: P2 normal (vote) TargetMilestone: --- Assigned To: Apache HTTPD Bugs Mailing List URL: Keywords: Depends on: Blocks: Show
Proxy: Error Reading Status Line From Remote Server
dependency tree Reported: 2006-05-06 13:18 UTC by Jan P. Sorensen Modified: 2007-07-28 02:37 UTC (History) CC List: 2 users (show) han44solo pupilla Attachments 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 Jan P. Sorensen 2006-05-06 13:18:31 UTC I (20014)internal error: proxy: error reading status line from remote server am running a reverse proxy server. Since I upgraded to Apache 2.2.0 (and 2.2.2) I have had a lot of errors: "error reading status line" The relevant part of the config file is:
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings ah00898: error reading from remote server returned by and policies of this site About Us Learn more about Stack Overflow
(104)connection Reset By Peer: Proxy: Error Reading Status Line From Remote Server
the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges
Proxy-initial-not-pooled
Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: https://bz.apache.org/bugzilla/show_bug.cgi?id=39499 Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Intermittent error when using mod_proxy to do reverse proxy to SOAP service up vote 13 down vote favorite 5 I get this error every few minutes when using mod_proxy as a reverse proxy to a SOAP web service. There's probably 3 or http://serverfault.com/questions/206738/intermittent-error-when-using-mod-proxy-to-do-reverse-proxy-to-soap-service 4 requests going per seconds so we're talking around 1 or 2 out of every thousand that have this error. [Tue Nov 23 11:44:14 2010] [error] [client 172.16.1.31] (20014)Internal error: proxy: error reading status line from remote server soap1.server:8888 [Tue Nov 23 11:44:14 2010] [error] [client 172.16.1.31] proxy: Error reading from remote server returned by /someapp/path/to/web/service This causes the request to fail. If I have the client connect directly to the soap server without using the proxy, success is 100% so the problem appears to be in the proxy The configuration looks like this. The purpose is to switch to a backup server if the primary one is unavailable:
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://serverfault.com/questions/185894/proxy-error-502-reason-error-reading-from-remote-server-with-apache-2-2-3-de the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault http://apache-http-server.18135.x6.nabble.com/mod-proxy-error-reading-status-line-td5003910.html Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign error reading 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 Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3 (Debian) mod_proxy and Jetty 6.1.18 up vote 46 down vote favorite 23 Apache is receiving requests at port :80 and proxying them to error reading status Jetty at port :8080 The proxy server received an invalid response from an upstream server The proxy server could not handle the request GET /. My dilemma: Everything works fine normally (fast requests, few seconds or few tens of seconds long requests are processed ok). Problems occur when request processing takes long (few minutes?). If I issue request instead directly to Jetty at port :8080 the request is processed OK. So problem is likely to sit somewhere between Apache and Jetty where I am using mod_proxy. How to solve this? I have already tried some "tricks" related to KeepAlive settings, without luck. Here is my current configuration, any suggestions? #keepalive Off ## I have tried this, does not help #SetEnv force-proxy-request-1.0 1 ## I have tried this, does not help #SetEnv proxy-nokeepalive 1 ## I have tried this, does not help #SetEnv proxy-initial-not-pooled 1 ## I have tried this, does not help KeepAlive 20 ## I have tried this, does not help KeepAliveTimeout 600 ## I have tried this, does not help ProxyTimeout 600
this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ mod_proxy error reading status line We're using apache mod_proxy to proxy requests to jboss servers on different hosts. We've noticed that we're getting sporadic http 502 response codes. In the apache error file, I see LOTS of these errors: [Tue Feb 26 13:55:49 2013] [error] [client 10.16.0.211] (70014)End of file found: proxy: error reading status line from remote server remotejboss-b [Tue Feb 26 13:55:49 2013] [error] [client 10.16.0.211] proxy: Error reading from remote server returned by /STRService/services/SoapToRestSOAP [Tue Feb 26 13:55:49 2013] [error] [client 10.16.0.211] no acceptable variant: /usr/local/apache2/error/HTTP_BAD_GATEWAY.html.var A bit of digging around, and I find this bug report: https://issues.apache.org/bugzilla/show_bug.cgi?id=37770This bug talks about setting 3 environment variables to resolve the issue. SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 SetEnv proxy-initial-not-pooled 1 My main problem is that I'm being asked to recreate this in our test environment before promoting this change to the production apache server. Recreating this has proven to be VERY cumbersome. I look at what I can do on both sides of the connection (jboss and apache) to try and recreate the issue. I see things like connection timeout and pool size, etc. Any suggestions on how I might be able to get this to occur in my test area would be GREAT!. Thanks, -mark- --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] Tom Evans-3 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: mod_proxy error reading status line On Wed, Feb 27, 2013 at 2:59 PM, Mark Lybarger <[hidden email]> wrote: > We're using apache mod_proxy to proxy requests to jboss servers on > different hosts. We've noticed that we're getting sporadic http 502 > response codes. In the apache error file, I see LOTS of these errors: