[pca] April 8th proxy xref?

[Ben Taylor]

On Mon, Apr 27, 2009 at 4:49 PM, Jon Whitehouse
<Jonathan.Whitehouse at zimmer.com> wrote:
> Ok. I’m really confused  I have a proxy setup for pca.  Everything appears
> setup correctly.
>
>
>
> On proxy:
>
>
>
> Webserver:
>
> -rwxr-xr-x   1 webservd webservd  138810 Apr  8 07:59 pca-proxy.cgi
>
>
>
> -rw-------   1 webservd webservd      93 Mar 17 11:24 /etc/pca-proxy.conf
>
> -rw-r--r--   1 700      root         312 Apr 16 17:01 /etc/pca.conf
>
>
>
> # cat /etc/pca-proxy.conf
>
> xrefdir=/pca-proxy/pca
>
> patchdir=/pca-proxy/pca
>
> user=xxxx
>
> passwd=xxxx
>
>
>
> # cat /etc/pca.conf
>
> # PCA Patching Directories
>
> patchdir=/pca-proxy/pca
>
> # PCA Proxy
>
> wgetproxy=http://proxy-server:8080
>
> # PCA - Sun ID & Password
>
> user=xxxx
>
> passwd=xxxx
>
> # Try to download 5x
>
> dltries=5
>
> # Keep pca updated
>
> update=auto
>
> # Write successful patches to user syslog
>
> syslog=user
>
> # set ssprot
>
> ssprot=http
>
>
>
> Now when I run pca it looks correct:
>
>
>
> # pca
>
> Using /var/tmp/patchdiag.xref from Apr/24/09
>
>
>
> Now if I go to another box that I want to connect to the main server and run
> pca
>
>
>
> # pca
>
> Using /tmp/patchdiag.xref from Apr/08/09
>
>
>
> Why is it using one from April 8th??? It doesn’t matter what other box I go
> to, it always trys to default to April 8th….  Here is the config from a box
> that keeps saying it only has one from the 8th... I’m stumped.
>
>
>
> # cat /etc/pca.conf
>
> # Patch Check Advanced - Configuration File
>
> # Conf File Updated: 04/27/2009
>
> #
>
> # Patch Directories
>
> patchdir=/tmp
>
> xrefdir=/tmp
>
> # Use Local Proxy
>
> patchurl=http://pca-proxybox/cgi-bin/pca-proxy.cgi
>
> xrefurl=http://pca-proxybox/cgi-bin/pca-proxy.cgi
>
> # Try to download 5x
>
> dltries=5
>
> # Keep pca updated
>
> pcaurl=http://pca-proxybox/cgi-bin/pca-proxy.cgi
>
> # Write successful patches to user syslog
>
> syslog=user
>
> # Do not use https
>
> ssprot=http
>


Run in debug/verbose mode, then remove the offending
/var/tmp/patchdiag.xref file
and run again in debug/verbose mode.  there may be an issue with the proxy
and how that update is being handled...

Ben