Hi Maarten,
On Wed, June 24, 2009 14:10, Maarten Litmaath wrote:
>> # echo X509_USER_PROXY
>> globus-tmp.grid239.10425.0
>
> That seems wrong! What if the job changes its working directory?
> Then it no longer has a proxy...
Ohh, sorry, my mistake. I mistyped the echo result, $X509_USER_PROXY
contained this absolute path: /tmp/globus-tmp.grid239.10425.0
So, I suppose changing the working directory doesn't affect if the job can
reach the proxy or not.
> BTW, there are mistakes in the VOMS configuration of your SE:
>
> -----------------------------------------------------------------------------
> $ uberftp grid143.kfki.hu
> 220 grid143.kfki.hu GridFTP Server 2.3 (gcc64dbg, 1144436882-63) ready.
> 230 User opssgm logged in.
> uberftp> cd /etc/grid-security/vomsdir/cms
> uberftp> dir
> -rw-r--r-- 1 root root 154 Jan 31 16:38 voms.cern.ch.lsc
> drwxr-xr-x 8 root root 4096 Mar 28 04:02 ..
> drwxr-xr-x 2 root root 4096 Jan 31 16:38 .
> uberftp> cat voms.cern.ch.lsc
> /DC=ch/DC=cern/OU=computers/CN=voms.cern.ch
> /DC=ch/DC=cern/CN=CERN Trusted Certification Authority
> /DC=ch/DC=cern/CN=CERN Trusted Certification Authority
> uberftp> quit
> -----------------------------------------------------------------------------
>
> 1. The syntax of that file is wrong: the last line should not be there.
> 2. You also should have such a file for lcg-voms.cern.ch.
>
> Look into /opt/glite/yaim/examples/siteinfo/site-info.def for correct
> definitions of the VO_*_VOMSES variables.
>
> However, these mistakes do not explain the problem, since the SE does
> have the VOMS server certificates in /etc/grid-security/vomsdir.
>
Thank you very much for pointing this out! I will fix this problem as soon
as possible.
Best regards,
Benjamin
|