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

[Ian Stokes-Rees <ijstokes@xxxxxxxxxxxxxxxxxxx>]

 This is interesting.  I no longer have the problem.  Perhaps Peter (who
has also chimed in on this thread, and is our group's Condor sys admin)
made some changes that caused this all to work.  If anyone is still
interested in further details, read on.

Thanks,

Ian

> I misread your original email. I thought some of the jobs within the dag were grabbing the proxy from the wrong location. It's odd that condor_submit_dag is looking for a proxy at all. What authentication methods is Condor configured to use on your machine?

On the submit side, I don't see anything from condor_config_val.  This
is running 7.4.3.

On the pool side, which is running 7.5.3, I have:

$ condor_config_val -dump | grep -e SEC -e X509
SCHEDD_DEBUG = D_SECURITY
SEC_CLIENT_AUTHENTICATION = OPTIONAL
SEC_CLIENT_ENCRYPTION = OPTIONAL
SEC_CLIENT_INTEGRITY = OPTIONAL
SEC_DAEMON_SESSION_DURATION = 50000
SEC_DEFAULT_AUTHENTICATION = REQUIRED
SEC_DEFAULT_AUTHENTICATION_METHODS = FS,GSI
SEC_DEFAULT_ENCRYPTION = OPTIONAL
SEC_DEFAULT_INTEGRITY = REQUIRED
SEC_ENABLE_MATCH_PASSWORD_AUTHENTICATION = TRUE
SEC_READ_AUTHENTICATION = OPTIONAL
SEC_READ_ENCRYPTION = OPTIONAL
SEC_READ_INTEGRITY = OPTIONAL
SUBMIT_EXPRS =  JOBGLIDEIN_Site X509USERPROXY
X509USERPROXY = /tmp/x509up_u1004

> Also, can you run condor_submit_dag with the -no_submit option and send me the resulting submit file?

$ condor_submit_dag -no_submit -debug 2 -import_env -outfile_dir
../config ../config/yn_test.dag

produces the file you can find here:

http://dl.dropbox.com/u/1561496/shared/yn_test.dag.condor.sub

$ condor_submit ../config/yn_test.dag.condor.sub

then runs successfully.  This is includes the -import_env setting, which
it was suggested could help things run