[pca] Downloading patches from proxy
Martin Paul
martin at par.univie.ac.at
Tue Feb 8 09:18:36 CET 2011
Fairburn, Jeremy wrote:
> The apache server is the local caching proxy as well. I am trying to
> download the patches from a server without access to the internet
> through the local caching proxy.
Ok. And the server running the PCA local caching proxy has a direct connection
to the Internet, or does it have to go through a standard web proxy? If not,
your setup can be simplified.
> Pca.conf of client:
>
> user=xxxxxx
> passwd=xxxxxxx
> debug=1
As you are using a PCA local caching proxy, it's not necessary to set
user/passwd in pca.conf on the client. Setting it on the PCA proxy is enough -
so remove these.
> pca-proxy.conf of local caching proxy:
>
> xrefdir=/patches
> patchdir=/patches
> wgetproxy=http://servername:portnumber
> dltries=5
> threads=5
> user=Oracle username
> passwd=Oracle password
> debug=1
You set wgetproxy here, so you tell wget that it can't connect to the Internet
directly, but has to go through a web proxy. Is this correct, and is
"servername" the same machine running the PCA local caching proxy? It is *not*
necessary to set "wgetproxy" if only a PCA local caching proxy is involved.
Please remove the "threads" setting here. It doesn't make sense on a PCA proxy,
and might introduce other problems.
> Changed values from wgetrc of client:
>
> http_proxy = http://servername:portnumber/
> https_proxy = http://servername:portnumber/
> ftp_proxy = http://servername:portnumber/
As the client is configured to use a PCA local caching proxy, it will only
connect to that server and not to the Internet directly. So you do not need
these settings on the client.
> Debug output of trying to download one patch that does not reside on the
> proxy server:
> ...
> --2011-02-07 13:18:35-- http://
> servername:portnumber/cgi-bin/pca-proxy.cgi?144221-02
> Resolving servername... x.x.x.x
> Connecting to servername|x.x.x.x|:portnumber... connected.
> Proxy request sent, awaiting response... 500 Internal Server Error
> 2011-02-07 13:18:35 ERROR 500: Internal Server Error.
So the PCA local caching proxy fails with a rather generic error. Please make
the above mentioned changes in your setup, re-run this same pca command, and
show me debug output of this command, but also debug output from the PCA local
caching proxy, which is logged to /var/tmp/pca-proxy-debug.txt on the server.
> Removing /tmp/pca.803954
> Failed (Error 500: Internal Server Error)
> Trying Oracle
> Trying https://getupdates.oracle.com/ (1/1)
As downloading the patch from the PCA proxy failed, pca on the client now tries
to connect to the Oracle server through your local web proxy, but it fails with
an error from the web proxy:
> Connecting to servername|x.x.x.x|:portnumber... connected.
> Proxy tunneling failed: Authorization RequiredUnable to establish SSL
> connection.
That's a problem with your local web proxy, but we'll ignore that. In a working
PCA local caching proxy setup, the PCA client will never try to connect to the
Internet at all, as the PCA proxy will fulfill all download queries.
Martin.
More information about the pca
mailing list