 |
 |
Hi Benjamin, >>There appears to be a problem with the job's proxy: >>either X509_USER_PROXY does not point to a proxy at all, >>or the mode or ownership of the file is wrong. >> > > > I submitted a test job which "echoes" the $X509_USER_PROXY and examines > its ownership and mode. I think its totally correct: > > # 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... > # ls -l globus-tmp.grid239.10425.0 > -rw------- 1 hungrid041 hungrid 9617 Jun 24 13:18 globus-tmp.grid239.10425.0 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.