Mailing List ArchivesAuthenticated access |
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesAuthenticated access |
|
I have no files in this directory. I only have one "POOL" file in the "passwords.d" directory which was generatedÂ
in the master (install) and copied to the other machines in the cluster.
Concerning ma config
# cat condor_config |
egrep "^[A-Z]"
RELEASE_DIR = /usr
LOCAL_DIR = /var
LOCAL_CONFIG_FILE = /etc/condor/condor_config.local
REQUIRE_LOCAL_CONFIG_FILE = false
LOCAL_CONFIG_DIR = /etc/condor/config.d
ALLOW_WRITE = *.xxx.yy
LEGACY_ALLOW_SEMANTICS = TRUE
RUNÂÂÂÂ = $(LOCAL_DIR)/run/condor
LOGÂÂÂÂ = $(LOCAL_DIR)/log/condor
LOCKÂÂÂ = $(LOCAL_DIR)/lock/condor
SPOOLÂÂ = $(LOCAL_DIR)/lib/condor/spool
EXECUTE = $(LOCAL_DIR)/lib/condor/execute
BINÂÂÂÂ = $(RELEASE_DIR)/bin
LIB = $(RELEASE_DIR)/lib64/condor
INCLUDE = $(RELEASE_DIR)/include/condor
SBINÂÂÂ = $(RELEASE_DIR)/sbin
LIBEXEC = $(RELEASE_DIR)/libexec/condor
SHAREÂÂ = $(RELEASE_DIR)/share/condor
PROCD_ADDRESS = $(RUN)/procd_pipe
JAVA_CLASSPATH_DEFAULT = $(SHARE) $(SHARE)/scimark2lib.jar
.
SSH_TO_JOB_SSHD_CONFIG_TEMPLATE =
/etc/condor/condor_ssh_to_job_sshd_config_template
CONDOR_HOST = monmaster.xxx.yy
DAEMON_LIST = MASTER, SCHEDD
and concerning the security mode
config.d/00-htcondor-9.0.config:use security:recommended_v9_0
This whole config works very well with 23.5.2-1.e9 but not in 23.6.1-1.el9
Reading https://htcondor-wiki.cs.wisc.edu/index.cgi/wiki?p=UpgradingFromEightNineToNineZero I tried the following
in the whole cluster but it's not the solution
# condor_check_password --truncate
Carlos
What are the ownership and permissions of all of the files inside of the directory /etc/condor/tokens.d/? - Jaime On Apr 23, 2024, at 6:18âAM, Carlos Carranza <carranza@xxxxxxxxxxxxx> wrote: Hi, the version in the submit machine is 23.6.1-1.el9 and the version in the other machines is 23.5.2-1.el9-23.5.2-1.el9 . If downgrade my submit machine to 23.5.2-1 everything comes back normal and the jobs run. Le repertoire tokens.d est drwx------ 2 root root 6 Mar 14 03:13 tokens.d Carlos On 4/22/24 21:59, Jaime Frey via HTCondor-users wrote: What is the version of HTCondor on your submit machine (the machine running your condor_schedd)? Also, check the files under /etc/condor/tokens.d/. They should owned and readable only by root. - Jaime On Apr 17, 2024, at 8:48âAM, Carlos Carranza <carranza@xxxxxxxxxxxxx><mailto:carranza@xxxxxxxxxxxxx> wrote: I configured a htcondor cluster ( not CE ) on RockyLinux9 using htcondor-release-23.x-1.el9.noarch and it worked very well. After updater my condor client ( not the master, the machine from where I submit jobs ). In fact, I update only python3-condor-23.5.2-1.el9.x86_64 to python3-condor-23.6.1-1.el9.x86_64 only in the machine where I submit my jobs. Since then my jobs remain IDLE in the master, and in the SchedLog file I found 4/17/24 15:31:35 (pid:28306) AUTH_ERROR: Cannot resolve network address for KDC in requested realm 04/17/24 15:31:35 (pid:28306) SECMAN: required authentication with collector martb05.in2p3.fr<http://martb05.in2p3.fr/> failed, so aborting command DC_START_TOKEN_REQUEST. 04/17/24 15:31:35 (pid:28306) Failed to request a new token: DAEMON:1:failed to start command for token request with remote daemon at '<134.158.20.59:9618?alias=martb05.in2p3.fr<http://martb05.in2p3.fr/>>'.|AUTHENTICATE:1003:Failed to authenticate with any method|AUTHENTICATE:1004:Failed to authenticate using SSL|AUTHENTICATE:1004:Failed to authenticate using SCITOKENS|AUTHENTICATE:1004:Failed to authenticate using KERBEROS|AUTHENTICATE:1004:Failed to authenticate using FS Note: martb05 is the master machine Any help or advice will be very well received .... -- -------------------------- Carlos Carranza Grid and CLoud Computing carranza@xxxxxxxxxxxxx<mailto:carranza@xxxxxxxxxxxxx><mailto:carranza@xxxxxxxxxxxxx><mailto:carranza@xxxxxxxxxxxxx> IN2P3 - CPPM 04 91 82 72 10 -------------------------- _______________________________________________ HTCondor-users mailing list To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx<mailto:htcondor-users-request@xxxxxxxxxxx> with a subject: Unsubscribe You can also unsubscribe by visiting https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users The archives can be found at: https://lists.cs.wisc.edu/archive/htcondor-users/ _______________________________________________ HTCondor-users mailing list To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx<mailto:htcondor-users-request@xxxxxxxxxxx> with a subject: Unsubscribe You can also unsubscribe by visiting https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users The archives can be found at: https://lists.cs.wisc.edu/archive/htcondor-users/ -- -------------------------- Carlos Carranza Grid and CLoud Computing carranza@xxxxxxxxxxxxx<mailto:carranza@xxxxxxxxxxxxx> IN2P3 - CPPM 04 91 82 72 10 -------------------------- _______________________________________________ HTCondor-users mailing list To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx<mailto:htcondor-users-request@xxxxxxxxxxx> with a subject: Unsubscribe You can also unsubscribe by visiting https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users The archives can be found at: https://lists.cs.wisc.edu/archive/htcondor-users/
_______________________________________________ HTCondor-users mailing list To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a subject: Unsubscribe You can also unsubscribe by visiting https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users The archives can be found at: https://lists.cs.wisc.edu/archive/htcondor-users/
-- -------------------------- Carlos Carranza Grid and CLoud Computing carranza@xxxxxxxxxxxxx IN2P3 - CPPM 04 91 82 72 10 --------------------------