It would only be trying to resolve the KDC address if you have KERBEROS authentication enabled. Do you?
I believe Kerberos requires DNS to work and it appears that the way you are configured it isn't.
(presuming that 192.168.1.197 is the only network that's available on the CM)
Steve
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Justin Killebrew via HTCondor-users <htcondor-users@xxxxxxxxxxx>
Sent: Friday, September 12, 2025 11:40 AM To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx> Cc: Justin Killebrew <jk@xxxxxxx> Subject: [HTCondor-users] authentication error(s) [EXTERNAL] – This message is from an external sender This is a fresh Ubuntu 24.04 install. 1 central manager (CM), 1 execute point (EP). The CM is
bench9.timehole.org, 192.168.1.197.
EP MasterLog errors:
AUTH_ERROR: Cannot resolve network address for KDC in requested realm
SECMAN: required authentication with collector bench9.timehole.org failed ...
ERROR: AUTHENTICATE:1003:Failed to authenticate with any method ...
Another symptom/problem:
on the EP:
$ condor_config_val trust_domain
bench9.timehole.org
but on the CM:
$ condor_config_val trust_domain
192.168.1.197
I have added this to the EP /etc/condor/condor_config
ALLOW_WRITE = *.timehole.org
TRUST_DOMAIN = 192.168.1.197
STARTD_DEBUG = D_SECURITY
But that does not change the condor_config_val trust_domain. Is there another way to set the trust_domain to the IP address? Would that fix the AUTH_ERROR: Cannot resolve network address problem?
Thanks for the help.
JK
|