[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Condor doesn't appear to respect X509_USER_PROXY

On Aug 24, 2010, at 10:56 AM, Ian Stokes-Rees wrote:

I have my X509_USER_PROXY pointing to a valid proxy cert in my
NFS-mounted home directory (/nfs/home/ijstokes/.globus/x509up_u1004),
but condor seems to insist on looking for it in /tmp, despite what the
docs say here:


I can copy the proxy cert to /tmp, but I need it in the NFS location for
other services on other hosts, and copying it around is just asking for
problems later, when one expires, and the other is renewed/updated.

Is this a bug, or am I doing something wrong?  Trace below.

The problem is that by default, the environment variables that exist when you run condor_submit aren't propagated to the environment that the condor_dagman job runs under. So when condor_dagman runs condor_submit to run jobs in the dag, condor_submit doesn't see X509_USER_PROXY.

You have two options:
1) Do as Zach suggests and set x509userproxy in the dag node submit files.
2) Use the -import_env argument to condor_submit_dag.

Thanks and regards,
Jaime Frey
UW-Madison Condor Team