[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Configuring a default scheduler address
- Date: Fri, 18 Feb 2022 17:15:54 +0100
- From: Javier Barbero GÃmez <jbarbero@xxxxxx>
- Subject: Re: [HTCondor-users] Configuring a default scheduler address
I found a weird behaviour today related to this issue.
Job submission works without a problem, but when using the "condor_q"
command, no jobs appear after submitting them. If you use the "condor_q
-user <username>", same thing. But if you use "condor_q -all", then all
users' jobs appear, including your own.
If you do this on the machine where the scheduler is running, this does
not happen: running "condor_q" shows that user's queued jobs.
I suppose this is an issue with user mapping across machines, but I
thought that the authentication method managed that already.
El 15/02/2022 a las 21:46, Todd Tannenbaum escribiÃ:
On 2/15/2022 2:29 PM, Javier Barbero wrote:
That is exactly what I needed. Thank you very much Todd! Everything
is up and running as I wanted now.
Fantastic!Â Glad we could help and thatÂ you got it working.
El 15/2/22 a las 20:47, Todd Tannenbaum escribiÃ:
On 2/15/2022 11:13 AM, Javier Barbero GÃmez wrote:
Hi, this is related to my previous thread about setting up File
System Remote authentication, as it is part of my goal of using a
single scheduler for the whole cluster, but I decided to ask
separately as it is a separate question.
I want to achieve the following behaviour: all jobs submitted
through "condor_submit" from any machine in my cluster should be
sent to the same scheduler in a set machine. Similarly, when using
"condor_q" this scheduler should be queried. Usually this is
achieved using the "-name" option in both cases and specifying the
address there, but I want to make it transparent to users so they
do not have to type it out every time or remember to include this
in their scripts.
I believe what you want to do is set SCHEDD_HOST config knob in the
condor_config file(s) on your machines.Â For instance, if your
ÂÂÂ SCHEDD_HOST = submit05.foo.edu
Then whenever users enter "condor_q", "condor_rm", "condor_submit",
etc, it will default to using the schedd at "submit05.foo.edu", just
as if you had used the "-name" argument. This also works with the
Python API (bindings) as expected.
Also you may find the below HOWTO of interest:
Hope the above helps.
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx
You can also unsubscribe by visiting
The archives can be found at:
Todd Tannenbaum<tannenba@xxxxxxxxxxx> University of Wisconsin-Madison
Center for High Throughput Computing Department of Computer Sciences
Calendar:https://tinyurl.com/yd55mtgd 1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132 Madison, WI 53706-1685