Mailing List ArchivesAuthenticated access |
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesAuthenticated access |
|
|
Hi Cole, Thanks you for your answer, but I ended up finding the setting that worked for me. All I needed to do was to add the two following lines to the 00-minicondor file: SEC_DEFAULT_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_CLIENT_AUTHENTICATION_METHODS = FS, CLAIMTOBE After a condor_reconfig, I can submit jobs from the host machine and even from other containers
😊 That being said, what I cannot do is run the condor_reconfig command itself from host machine or containersâ I get the exact same error when I try to do so, so I tried adding all the other authentication methods to the file as well: SEC_DEFAULT_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_CLIENT_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_READ_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_WRITE_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_ADMINISTRATOR_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_CONFIG_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_DAEMON_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_NEGOTIATOR_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_ADVERTISE_MASTER_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_ADVERTISE_STARTD_AUTHENTICATION_METHODS = FS, CLAIMTOBE SEC_ADVERTISE_SCHEDD_AUTHENTICATION_METHODS = FS, CLAIMTOBE I also set ALLOW_ADMINISTRATOR = * and
SEC_DEFAULT_AUTHENTICATION = OPTIONAL, but that does not fix itâ Here is what the MasterLog says: GSS Major Status: General failure GSS Minor Status Error Chain: globus_gsi_gssapi: Error with GSI credential globus_gsi_gssapi: Error with gss credential handle globus_credential: Valid credentials could not be found in any of the possible locations specified by the credential search order. Valid credentials could not be found in any of the possible locations specified by the credential search order. Attempt 1 globus_credential: Error reading host credential globus_sysconfig: Could not find a valid certificate file: The host cert could not be found in: 1) env. var. X509_USER_CERT 2) /etc/grid-security/hostcert.pem 3) $GLOBUS_LOCATION/etc/hostcert.pem 4) $HOME/.globus/hostcert.pem The host key could not be found in: 1) env. var. X509_USER_KEY 2) /etc/grid-security/hostkey.pem 3) $GLOBUS_LOCATION/etc/hostkey.pem 4) $HOME/.globus/hostkey.pem Attempt 2 globus_credential: Error reading proxy credential globus_sysconfig: Could not find a valid proxy certificate file location globus_sysconfig: Error with key filename globus_sysconfig: File does not exist: /tmp/x509up_u0 is not a valid file Attempt 3 globus_credential: Error reading user credential globus_sysconfig: Error with certificate filename: The user cert could not be found in: 1) env. var. X509_USER_CERT 2) $HOME/.globus/usercert.pem 3) $HOME/.globus/usercred.p12 03/02/23 15:56:02 DC_AUTHENTICATE: required authentication of 127.0.0.1 failed: AUTHENTICATE:1003:Failed to authenticate with any method|AUTHENTICATE:1004:Failed to authenticate using SCITOKENS|AUTHENTICATE:1004:Failed
to authenticate using GSI|GSI:5003:Failed to authenticate. Globus is reporting error (851968:203). There is probably a problem with your credentials. (Did you run grid-proxy-init?)|AUTHENTICATE:1004:Failed to authenticate using KERBEROS|AUTHENTICATE:1004:Failed
to authenticate using IDTOKENS|AUTHENTICATE:1004:Failed to authenticate using FS|FS:1004:Unable to lstat(/tmp/FS_XXXeQWHFT) Thanks, GaÃtan
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of Cole Bollig via HTCondor-users
CAUTION:
This email originated from outside of Terma. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Gaetan, I have a couple of questions about your setup:
-Cole Bollig From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Gaetan Geffroy <gage@xxxxxxxxx> Hi, I use a htcondor/mini Docker container to test and prototype on Condor. If I open a bash inside the container I can use the commands just fine, but what I want to do is to have access to then and the Python bindings from the host machine, or from another container.
I run the container like this: docker run -it --network host --name condor --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ htcondor/mini:9.0.16-el7 Then, I take a copy of the config file 00-minicondor, put it on the host machine and have the CONDOR_CONFIG env var to point at it. This works fine for things like condor_q or condor_status, but when I try to use condor_submit I get the following: Submitting job(s) ERROR: Failed to connect to local queue manager AUTHENTICATE:1003:Failed to authenticate with any method AUTHENTICATE:1004:Failed to authenticate using SCITOKENS AUTHENTICATE:1004:Failed to authenticate using GSI GSI:5003:Failed to authenticate. Globus is reporting error (851968:101). There is probably a problem with your credentials. (Did you run grid-proxy-init?) AUTHENTICATE:1004:Failed to authenticate using KERBEROS AUTHENTICATE:1004:Failed to authenticate using IDTOKENS AUTHENTICATE:1004:Failed to authenticate using FS So, I tried things like to set SEC_DEFAULT_AUTHENTICATION = NEVER, SEC_DEFAULT_AUTHENTICATION_METHODS = CLAIMTOBE, FS, ALLOW_WRITE = * and use security:host_based. None of these work. What more can I do if even disabling authentication did not work ? Thanks, GaÃtan
Attention: |