Proxy Error Reading Status Line From Remote Server Localhost
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 error reading from remote server returned by of this site About Us Learn more about Stack Overflow the company Business ah00898: error reading from remote server returned by Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question
Internal Error Proxy Error Reading Status Line From Remote Server Localhost
_ 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: Anybody can ask a
(104)connection Reset By Peer: Proxy: Error Reading Status Line From Remote Server
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 4 requests going per seconds so setenv proxy-initial-not-pooled 1 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:
Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug632407 - proxy: error reading status line from
(70007)the Timeout Specified Has Expired: Proxy: Error Reading Status Line From Remote Server
remote server Summary: proxy: error reading status line from remote server Status: CLOSED ERRATA setenv force-proxy-request-1.0 1 Aliases: None Product: Red Hat Enterprise Linux 5 Classification: Red Hat Component: httpd (Show other bugs) Sub Component: --- Version: 5.5 Hardware: proxy-initial-not-pooled example All Linux Priority urgent Severity urgent TargetMilestone: rc TargetRelease: --- Assigned To: Joe Orton QA Contact: Zbysek MRAZ Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: 590060 Show dependency tree /graph Reported: 2010-09-09 16:48 http://serverfault.com/questions/206738/intermittent-error-when-using-mod-proxy-to-do-reverse-proxy-to-soap-service EDT by Bryan Mason Modified: 2013-07-03 09:12 EDT (History) CC List: 15 users (show) cww ebenes eliningt gerrit.slomma hampus.lundqvist jagee jcastillo jwest kslinux.team mfiteisa mpoole rhuang tao yasuhiro.ozone zzhou See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2011-07-21 04:51:20 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from https://bugzilla.redhat.com/show_bug.cgi?id=632407 Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) log of proxy-server (14.52 KB, text/plain) 2011-08-09 04:04 EDT, Gerrit Slomma no flags Details Add an attachment (proposed patch, testcase, etc.) External Trackers Tracker ID Priority Status Summary Last Updated Apache Bugzilla 37770 None None None Never Groups: None (edit) Description Bryan Mason 2010-09-09 16:48:32 EDT Description of problem: When attempting to access a backend IIS server through an Apache server running mod_proxy, the client receives a 502 error and lines smilar to the following appear in the Apache error log: [error] [client 10.1.2.3] proxy: error reading status line from remote server example.com [error] [client 10.1.2.3] proxy: Error reading from remote server returned by /example Version-Release number of selected component (if applicable): httpd-2.2.3-31.el5_4.4 How reproducible: 100% Steps to Reproduce: 1. Configure mod_proxy to proxy an IIS server 2. Attempt to access the IIS server through mod_proxy Actual results: 502 error Expected results: No error Additional info: This is the same problem as: https://issues.apache.org/bugzilla/show_bug.cgi?id=37770 Although Red Hat Bug 466723 would seem to indicate that this was resolved in RHEL 5.3, the patch included in the Apache Bug is not included in the latest version of the httpd package in RHEL 5. The RHEL 5.3 update to httpd rebased mod_proxy to upstream version 2.2.9, but comm
timeout specified has expired: proxy: error reading status line from remote server10-1Hendrik MeiffertFeb 06, 2014Since this morning I receive this error : (70007)The timeout specified has expired: proxy: error reading status line from remote server https://answers.atlassian.com/questions/259235/having-error-70007the-timeout-specified-has-expired-proxy-error-reading-status-line-from-remote-server I am using a Confluence Standalone version and we didn't change anything in http://stackoverflow.com/questions/169453/bad-gateway-502-error-with-apache-mod-proxy-and-tomcat our apache configuration. The other pages of that server are all running. Can it be connected to the current problems on atlassian.confluence.com? I mean for example the addons etc are connected to them even though we have a standalone version. Any ideas how to fix this problem ? I already put up the error reading timeout etc. without success like this : Keepalive=On retry=1 acquire=3000 timeout=600 proxytimeout 5400 timeout 5400
confluenceconfluence-administrationCommentCommentAdd your comment...4 answers210Andy Brook [The Plugin People]Feb 06, 2014>(70007)The timeout specified has expired: proxy: error reading status line from remote server Maybe it died? If you have confluence sitting under apache, and that is contactable, try connecting with a browser direct (and check what, if any proxy server you have set from remote server in your browser...) My guess is that the confluence instance is not responding. If you have access to the server, check if there is confluence process running? Also check the logs, if you see anything like OutOfMemory, DiskFull etc, can all be symptoms of a crashed confluence. > Can it be connected to the current problems on atlassian.confluence.com? I mean for example the addons etc are connected to them even though we have a standalone version. No, your addons are installed locally. Only checks for updates go there, and that wont break you if its down.CommentAndy Brook [The Plugin People]Feb 06, 2014depends onhow you installed it, there could be a script called from /etc/rc.local, or aservice in /etc/init.d/ "ps -ef | grep java" will list the java processes, check confluence isnt still running. Id be a little uncomfortable telling you how to kill processes if you dont already know, you may get the wrong one. if confluence lives on its own box, the easiest way (if the installed did the job properly) is to just reboot the box.Hendrik MeiffertFeb 06, 2014i guess it died. So how to resurrect it ? using ubuntu 12.04 server, can you help me
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 about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Bad Gateway 502 error with Apache mod_proxy and Tomcat up vote 39 down vote favorite 14 We're running a web app on Tomcat 6 and Apache mod_proxy 2.2.3. Seeing a lot of 502 errors like this: Bad Gateway! The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /the/page.do. Reason: Error reading from remote server If you think this is a server error, please contact the webmaster. Error 502 Tomcat has plenty of threads, so it's not thread-constrained. We're pushing 2400 users via JMeter against the app. All the boxes are sitting inside our firewall on a fast unloaded network, so there shouldn't be any network problems. Anyone have any suggestions for things to look at or try? We're heading to tcpdump next. UPDATE 10/21/08: Still haven't figured this out. Seeing only a very small number of these under load. The answers below haven't provided any magical answers...yet. :) java apache tomcat mod-proxy share|improve this question edited Oct 21 '08 at 19:45 community wiki 2 revsAlex Miller I am facing this problem for some time during my running application –Uday A. Navapara Mar 12 '15 at 5:27 add a comment| 7 Answers 7 active oldest votes up vote 32 down vote Just to add some specific settings, I had a similar setup (with Apache 2.0.63 reverse proxying onto Tomcat 5.0.27). For certain URLs the Tomcat server could take perhaps 20 minutes to return a page. I ended up modifying the following settings in the Apache configuration file to prevent it from timing out with its proxy operation (with a large over-spill factor in case Tomcat took longer to return a page): Timeout 5400 ProxyTimeout 5400 Some backgound ProxyTimeout alone wasn't enough. Looking at the documentation for Timeout I'm guessing (I'm not sure) that this is because while Apache is waiting for a response from Tomcat, there is no traffic flowing between Apache and the Browser (or whatever http client) - and so Apache closes down the connection to the browser. I found that if I left the Timeout setting at its default (300 seconds), then if