Apache Mod_proxy Error Reading Status Line From Remote Server
Contents |
Forgot Password Login: [x] First Last Prev Next This bug is not in your last search results. Bug48037 - mod_proxy_http does not handle proxy error reading status line from remote server localhost asynchronous keepalive close events correctly Summary: mod_proxy_http does not handle asynchronous keepalive internal error proxy error reading status line from remote server close events correctly Status: NEW Product: Apache httpd-2 Classification: Unclassified Component: mod_proxy_http Version: 2.0.63 Hardware: PC Linux Importance: P2 20014 internal error proxy error reading status line from remote server normal with 2 votes (vote) TargetMilestone: --- Assigned To: Apache HTTPD Bugs Mailing List URL: Keywords: Depends on: Blocks: Show dependency tree Reported: 2009-10-21 16:35 UTC by John Lightsey
Connection Reset By Peer Proxy Error Reading Status Line From Remote Server
Modified: 2016-08-01 03:04 UTC (History) CC List: 4 users (show) helen jd sokann williama_lovaton Attachments server config files (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 the timeout specified has expired proxy error reading status line from remote server 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 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 p
[x] First Last Prev Next This bug is 104 connection reset by peer proxy error reading status line from remote server not in your last search results. Bug37770 - proxy: error
Proxy-initial-not-pooled
reading status line from remote server (null) Summary: proxy: error reading status line from remote server
Ah00898: Error Reading From Remote Server Returned By
(null) Status: REOPENED Product: Apache httpd-2 Classification: Unclassified Component: mod_proxy Version: 2.2.3 Hardware: Sun Solaris Importance: P1 blocker with 29 votes (vote) TargetMilestone: --- Assigned https://bz.apache.org/bugzilla/show_bug.cgi?id=48037 To: Apache HTTPD Bugs Mailing List URL: http://extra.gatema.cz/Test42/Data.asmx Keywords: ErrorMessage Duplicates: 32731 37876 39499 39629 41150 44079 45588 46504 57520 (view as bug list) Depends on: Blocks: Show dependency tree Reported: 2005-12-03 13:40 UTC by Christophe Yayon Modified: 2015-10-27 07:35 UTC (History) CC List: 26 users (show) alejandro.cavallo https://bz.apache.org/bugzilla/show_bug.cgi?id=37770 anup.mittal apache bill+apache brett chris denis.kranjcec dkruglyak japs jconley jibanes jmehta jtharp kirant400 marado milan.pospisil mirkwood09+spamkill paul.kmiec ronn.chinowutthichai rvandolson suresh.pagadala tapan.nanawati thierry.trinh todorz vladap yneko Attachments backend connection race condition fix (untested) (2.88 KB, patch) 2007-12-07 07:31 UTC, Aleksey Midenkov Details | Diff Patch against trunk (1.71 KB, patch) 2008-07-31 13:23 UTC, Ruediger Pluem Details | Diff 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 Christophe Yayon 2005-12-03 13:40:17 UTC Hi all, I have configured httpd-2.2.0 (release) with mod_proxy and virtual hosting and when i stress it, even low (10 simultaneous users with Mercury Load Runner) i get some errors messages and status code 502 on the client browser. The problem occurs only when i do some load tests, when i request from single client i have no problem... My error.log
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the http://serverfault.com/questions/206738/intermittent-error-when-using-mod-proxy-to-do-reverse-proxy-to-soap-service 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 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 up Here's error reading how it works: 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 12 down vote favorite 5 I get this error every few minutes when using mod_proxy as a reverse proxy to a SOAP web service. from remote server There's probably 3 or 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: