Apache2 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
Apache Error Reading Status Line From Remote Server
workings and policies of this site About Us Learn more about ah00898: error reading from remote server returned by Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions
Internal Error: Proxy: Error Reading Status Line From Remote Server
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 status line from remote server localhost 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. (70007)the timeout specified has expired: proxy: error reading status line 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:
Support Search GitHub This repository Watch 47 Star 220 Fork 26 icing/mod_h2 Code Issues 20 Pull
Proxy-initial-not-pooled
requests 0 Projects 0 Pulse Graphs New issue App behind mod_proxy connection reset by peer proxy error reading status line from remote server is only partially reachable #14 Closed jfmcbrayer opened this Issue Apr 17, 2015 · 12 comments
Setenv Proxy-initial-not-pooled
Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 2 participants jfmcbrayer commented Apr 17, 2015 This is, unfortunately, another vague-ish bug report. http://serverfault.com/questions/206738/intermittent-error-when-using-mod-proxy-to-do-reverse-proxy-to-soap-service I have ownCloud running in a kvm-qemu VM. The host machine is running my main apache server, to which I've just added mod_h2. The VM's apache is proxied like this: ProxyPass /owncloud http://192.168.122.135:80 max=20 ttl=120 retry=300 Most of the resources load, but for a few, I am getting a 502 Bad Gateway error. The errors https://github.com/icing/mod_h2/issues/14 in the ssl_errors.log on the host machine look like [Fri Apr 17 10:11:38.935081 2015] [proxy_http:error] [pid 17641:tid 140117117228800] (20014)Internal error: [client 74.254.77.254:9912] AH01102: error reading status line from remote server 192.168.122.135:80, referer: https://www.carcosa.net/owncloud [Fri Apr 17 10:11:38.935120 2015] [proxy:error] [pid 17641:tid 140117117228800] [client 74.254.77.254:9912] AH00898: Error reading from remote server returned by /owncloud/3rdparty/js/chosen/chosen.jquery.min.js, referer: https://www.carcosa.net/owncloud [Fri Apr 17 10:11:38.935175 2015] [proxy_http:error] [pid 17641:tid 140116915869440] (20014)Internal error: [client 74.254.77.254:9912] AH01102: error reading status line from remote server 192.168.122.135:80, referer: https://www.carcosa.net/owncloud [Fri Apr 17 10:11:38.935260 2015] [proxy:error] [pid 17641:tid 140116915869440] [client 74.254.77.254:9912] AH00898: Error reading from remote server returned by /owncloud/apps/contacts/js/loader.js, referer: https://www.carcosa.net/owncloud [Fri Apr 17 10:11:38.939905 2015] [proxy_http:error] [pid 17641:tid 140116941047552] (20014)Internal error: [client 74.254.77.254:9912] AH01102: error reading status line from remote server 192.168.122.135:80, referer: https://www.carcosa.net/owncloud [Fri Apr 17 10:11:38.939933 2015] [proxy:error] [pid 17641:tid 140116941047552] [client 74.254.77.254:9912] AH00898: Error reading from remote server returned by /owncloud/apps/search_lucene/js/checker.js, referer: https://www.carcosa.net/owncloud [Fri Apr 17 10:11:38.939982 2015] [proxy_http:error] [pid 17641:tid 140116974618368] (20014)Internal error: [client 74.254.77.254:9912] AH01102:
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 handle https://bz.apache.org/bugzilla/show_bug.cgi?id=48037 asynchronous keepalive close events correctly Status: NEW Product: Apache httpd-2 Classification: Unclassified Component: mod_proxy_http Version: 2.0.63 Hardware: PC Linux Importance: P2 normal with 2 votes (vote) TargetMilestone: --- Assigned To: Apache HTTPD Bugs Mailing List URL: http://grokbase.com/t/apache/users/135arymm6s/httpd-20014-internal-error-proxy-error-reading-status-line-from-remote-server 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 (3.82 error reading 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 is written, from remote server 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 configuration: ProxyPreserveHost On
using Apache 2.2.11 on CentOS, arch - x86 as write-through subversionproxy.Server version: Apache/2.2.11 (Unix)Server built: Apr 10 2010 16:04:54I have started getting the following error for last few days, which Ireally find strange :(20014)Internal error: proxy: error reading status line from remote servermyhostname.mydomain.com:80I found some information by googling and I found this thread :http://serverfault.com/questions/206738/intermittent-error-when-using-mod-proxy-to-do-reverse-proxy-to-soap-service. As per this thread I added the following in thehttpd.conf of write-throuh proxy :SetEnv force-proxy-request-1.0 1SetEnv proxy-nokeepalive 1But does not help. Also this thread also refershttp://httpd.apache.org/docs/2.2/mod/mod_proxy_http.html and it says :"proxy-initial-not-pooledIf this variable is set no pooled connection willbe reused if the client connection is an initial connection. This avoidsthe "proxy: error reading status line from remote server" error messagecaused by the race condition that the backend server closed the pooledconnection after the connection check by the proxy and before data sent bythe proxy reached the backend. It has to be kept in mind that setting thisvariable downgrades performance, especially with HTTP/1.0 clients."I tried to set this environment variable in write-through proxy'shttpd.conf but also of no help.I would appreciate any pointers on this.Thank you!Regards,Ravi. reply Tweet Search Discussions Search All Groups Apache users Related Discussions [users@httpd] (70007)The timeout specified has expired: proxy: error reading status line from remote server [users@httpd] proxy: error reading status line from remote server [users@httpd] error in mod_proxy? [users@httpd] Need help with #if DEBUGGING in proxy_http.c [users@httpd] apache 2.0.47 mod_proxy : proxy: error reading status line from remote server [users@httpd] CombinedLog with IPv6 [users@httpd] VirtualHost command line automation