[pca] PCA / cron

[McGranahan, Jamen]

Thanks for the advice Martin. I'll try that (I knew there had to be a way). On the authentication issue, yes, we discovered what the problem was. Unbeknown to me, the password had been changed, which explains why all of our PCA's were failing. Figures.... 
________________________________________
From: pca-bounces at lists.univie.ac.at [pca-bounces at lists.univie.ac.at] On Behalf Of Martin Paul [martin at par.univie.ac.at]
Sent: Saturday, September 26, 2009 10:52 AM
To: PCA (Patch Check Advanced) Discussion
Subject: Re: [pca] PCA / cron

Hi,

> If I run PCA manually, it does fine, so it seems
> to suggest something is wrong with the cron itself. The only thing I
> noticed between this one and the others is that for some reason, it
> is not connecting to https:// like the others and instead is trying
> to connect to just http://sunsolve.sun.com. Why would this be
> happening? Can I force PCA to always use https?

pca searches the PATH for wget binaries, and will use the "best" one it
finds. It will prefer HTTPS if it finds a wget which supports it. Most
probably there is no wget with HTTPS support in the default PATH used by
cron on the affected machine. When running it manually, you probably
have a different PATH leading to a "better" wget binary.

Either set PATH in your cron job, or use pcas' "--wget" option to point
it an SSL-enabled wget.

BTW - did you solve the other problem regarding the authentication errors?

hth,

Martin.