Error Reading From Server
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 error reading from server bf2 Stack Overflow the company Business Learn more about hiring developers or posting ads with
Error Reading From Remote Server
us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and 502 proxy error error reading from remote server network administrators. Join them; it only takes a minute: Sign 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 reading from remote server returned 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 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
Error Reading From Remote Server Returned By Apache
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 ## I have tried this, does not help NameVirtualHost *:80
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 error reading from remote server returned by /microsoft-server-activesync Stack Overflow the company Business Learn more about hiring developers or posting ads with error reading packet from server us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is
Error Reading Response From Server
a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Docker Debian apt Error Reading from Server up vote 8 down vote favorite http://serverfault.com/questions/185894/proxy-error-502-reason-error-reading-from-remote-server-with-apache-2-2-3-de 2 It would seem that apt-get is having issues connecting with the repository servers. I suppose it is likely compatibility issues, as mentioned here, however the proposed solution of apt-get clean does not work for me. Also I am surprised, if this is the case, that there are not more people having my issue. MWE Dockerfile FROM debian:jessie RUN apt-get clean && apt-get update && apt-get install -y --no-install-recommends \ http://stackoverflow.com/questions/32304631/docker-debian-apt-error-reading-from-server git $ docker build . docker build . Sending build context to Docker daemon 2.048 kB Step 0 : FROM debian:jessie ---> 4a5e6db8c069 Step 1 : RUN apt-get clean && apt-get update && apt-get install -y --no-install-recommends git ---> Running in 43b93e93feab Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB] ... some omitted ... Get:6 http://httpredir.debian.org jessie-updates/main amd64 Packages [3614 B] Fetched 9552 kB in 7s (1346 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: ... some omitted ... 0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded. Need to get 13.2 MB of archives. After this operation, 64.0 MB of additional disk space will be used. Get:1 http://security.debian.org/ jessie/updates/main libgnutls-deb0-28 amd64 3.3.8-6+deb8u2 [694 kB] ... some omitted ... Get:5 http://httpredir.debian.org/debian/ jessie/main libnettle4 amd64 2.7.1-5 [176 kB] Err http://httpredir.debian.org/debian/ jessie/main libffi6 amd64 3.1-2+b2 Error reading from server. Remote end closed connection [IP: 176.9.184.93 80] ... some omitted ... Get:25 http://httpredir.debian.org/debian/ jessie/main git amd64 1:2.1.4-2.1 [3624 kB] Fetched 13.2 MB in 10s (1307 kB/s) E: Failed to fetch http://httpredir.debian.org/debian/pool/main/libf/libffi/libffi6_3.1-2+b2_amd64.deb Error reading from server. Remote end closed connection [IP: 176.9.184.93 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? The comma
Sign in Pricing Blog Support Search GitHub This repository Watch 2 Star 2 Fork https://github.com/CGAL/cgal-testsuite-dockerfiles/issues/19 5 CGAL/cgal-testsuite-dockerfiles Code Issues 0 Pull requests 0 Projects 0 https://lists.debian.org/debian-devel/2015/07/msg00132.html Pulse Graphs New issue A random network error "Remote end closed connection" #19 Closed lrineau opened this Issue Jul 10, 2015 · 4 comments Projects None yet Labels question Milestone No milestone Assignees No one assigned 2 error reading participants The CGAL Project member lrineau commented Jul 10, 2015 That Debian build failed with: Failed to fetch http://httpredir.debian.org/debian/pool/main/g/glew/libglew1.10_1.10.0-3_amd64.deb Error reading from server. Remote end closed connection [IP: 5.153.231.35 80] Is there something we can do to protect our builds from those errors? lrineau added the question label Jul 10, 2015 error reading from The CGAL Project member bo0ts commented Jul 10, 2015 I'm wondering about that since those errors happened the first time and I cannot reproduce them locally. http://serverfault.com/questions/690639/api-get-error-reading-from-server-under-docker suggests to apt-get clean before an update. I don't see why that should be necessary (should update not check if the cache has been invalidated?!), but maybe it will help. The CGAL Project member lrineau commented Jul 10, 2015 Could it be that the base image contains a cache that apt uses? Then the `apt-get clean` cleans up the caches and re-initialize them. The CGAL Project member bo0ts commented Jul 10, 2015 17af85a adds apt-get clean. Let's reopen this if the problem keeps coming up. bo0ts closed this Jul 10, 2015 The CGAL Project member lrineau commented Jul 13, 2015 There was another build failure, today, but apt-get clean && apt-get update was called. I wonder why apt does not try wit
Leopold Palomo-Avellaneda