[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Arguments to condor_submit
- Date: Thu, 21 Dec 2017 15:32:49 -0500
- From: Larry Martell <larry.martell@xxxxxxxxx>
- Subject: Re: [HTCondor-users] Arguments to condor_submit
Is there some part of the initial condor setup I missed? I went over
the docs again and I don't think so.
On Thu, Dec 21, 2017 at 11:16 AM, Larry Martell <larry.martell@xxxxxxxxx> wrote:
> I get nothing back:
> $ condor_status -schedd -af Name
> But the schedd is running:
> $ ps -efal | grep condor
> 4 S condor 32054 1 0 80 0 - 18610 poll_s Dec12 ?
> 00:00:20 /usr/sbin/condor_master -f
> 4 S root 32112 32054 0 80 0 - 6652 poll_s Dec12 ?
> 00:10:25 condor_procd -A /var/run/condor/procd_pipe -L
> /var/log/condor/ProcLog -R 1000000 -S 60 -C 986
> 4 S condor 32113 32054 0 80 0 - 13531 poll_s Dec12 ?
> 00:00:55 condor_shared_port -f
> 4 S condor 32117 32054 0 80 0 - 20511 poll_s Dec12 ?
> 00:10:11 condor_collector -f
> 4 S condor 32122 32054 0 80 0 - 15762 poll_s Dec12 ?
> 00:41:59 condor_negotiator -f
> 4 S condor 32123 32054 0 80 0 - 27496 poll_s Dec12 ?
> 00:00:45 condor_schedd -f
> Same from python API:
>>>> coll = htcondor.Collector()
>>>> coll.query(htcondor.AdTypes.Schedd, projection=['Name'])
> On Thu, Dec 21, 2017 at 9:31 AM, Jason Patton <jpatton@xxxxxxxxxxx> wrote:
>> Each daemon (collector, negotiator, schedd, startd, etc.) is described with
>> a ClassAd, which has ClassAd attributes (Name, Machine, MyType, etc.), and
>> which is stored by the collector. So for the schedd name, you want to
>> provide the value of the Name attribute in the Schedd ClassAd for the schedd
>> you want to submit to. Per
>> http://research.cs.wisc.edu/htcondor/manual/current/12_Appendix_A.html the
>> Name is usually the machine name (which is usually the hostname) but if you
>> want to be sure, you can use the condor_status tool or the python bindings:
>> # query all schedd classads in the collector for the Name attribute
>> [jpatton@condor-el7 ~]$ condor_status -schedd -af Name
>>>>> coll = htcondor.Collector()
>>>>> coll.query(htcondor.AdTypes.Schedd, projection=['Name'])
>> [[ Name = "condor-el7.test" ]]
>> pool name is better described in the condor_status man page (probably
>> because it's more commonly used with condor_status):
>> -pool centralmanagerhostname[:portnumber]
>> (Query option) Query the specified central manager using an
>> optional port
>> number. condor_status queries the machine specified by the
>> variable COLLECTOR_HOST by default.
>> The hostname or ip where your collector lives, with the port if it's not
>> using the default. For example, if you needed to query a remote collector
>> for schedds:
>> [jpatton@condor-el7 ~]$ condor_status -pool 192.168.100.103 -schedd -af Name
>> Jason Patton
>> On Thu, Dec 21, 2017 at 4:58 AM, Larry Martell <larry.martell@xxxxxxxxx>
>>> The docs for condor_submit give this syntax:
>>> condor_submit -remote <schedd name> -pool <collector name> submit_file
>>> -remote schedd_name
>>> Submit to the specified condor_schedd, spooling all required input files
>>> over the network connection. schedd_name is the value of the Name ClassAd
>>> attribute on the machine where the condor_schedd daemon runs. This option is
>>> equivalent to using both -name and -spool.
>>> -pool pool_name
>>> Look in the specified pool for the condor_schedd to submit to. This option
>>> is used with -name or -remote.
>>> What specifically do I pass in for <schedd name> and <collector name>?
>>> Sorry if this is a very basic question, but I am new to condor and I have
>>> googled and googled and have not found the answer to this.