Re: [HTCondor-users] submitting jobs with API

[Jason Patton <jpatton@xxxxxxxxxxx>]

I don't have a solution, but hopefully I can help get the ball rolling. Without modifying my schedd config, I tried doing a remote submit following the same steps, which failed with the same error. The error is a little misleading/light on details, it's likely an authentication problem from not being on the same system as the schedd. Doing essentially the same thing using the client tools gives more info:

>>> schedd.submit(ad)

Traceback (most recent call last):

 File "<stdin>", line 1, in <module>

RuntimeError: Failed to connect to schedd.

$ condor_submit test.submit -remote condor-el7.test

Submitting job(s)

ERROR: Failed to connect to queue manager condor-el7.test

AUTHENTICATE:1003:Failed to authenticate with any method

AUTHENTICATE:1004:Failed to authenticate using GSI

GSI:5003:Failed to authenticate. Globus is reporting error (851968:50). 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 FS

You should see more details in SchedLog on your submit host.

Hopefully someone more knowledgable about setting up the schedd to accept remote job submissions can chime in. (ENABLE_SOAP and ENABLE_WEB_SERVER are probably not needed.)

Jason

On Tue, Dec 19, 2017 at 9:02 AM, Larry Martell <larry.martell@xxxxxxxxx> wrote:

On Tue, Dec 19, 2017 at 9:29 AM, Larry Martell <larry.martell@xxxxxxxxx> wrote:
> I am doing this:
>
> import htcondor
> import classad
> condor_host = '192.168.10.2'
> coll = htcondor.Collector(condor_host)
> schedd_ad = coll.locate(htcondor.DaemonTypes.Schedd)
> schedd = htcondor.Schedd(schedd_ad)
> ad = classad.ClassAd()
>
> # set up ad
>
> id = schedd.submit(ad)
>
> RuntimeError: 'Failed to connect to schedd.'
>
> On 192.168.10.2:
>
> 4 S condor  Â32054   Â1 0 80 Â0 - 18610 poll_s Dec12 ?
> 00:00:15 /usr/sbin/condor_master -f
> 4 S root   Â32112 Â32054 0 80 Â0 - 6652 poll_s Dec12 ?
> 00:07:51 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:44 condor_shared_port -f
> 4 S condor  Â32117 Â32054 0 80 Â0 - 20511 poll_s Dec12 ?
> 00:07:46 condor_collector -f
> 4 S condor  Â32122 Â32054 0 80 Â0 - 15856 poll_s Dec12 ?
> 00:31:40 condor_negotiator -f
> 4 S condor  Â32123 Â32054 0 80 Â0 - 18808 poll_s Dec12 ?
> 00:00:31 condor_schedd -f
>
> From the machine running the python code:
>
> $ nmap -p 9618 192.168.10.2
>
> Starting Nmap 6.40 ( http://nmap.org ) at 2017-12-19 09:28 EST
> Nmap scan report for 192.168.10.2
> Host is up (0.00018s latency).
> PORTÂ Â ÂSTATE SERVICE
> 9618/tcp open condor
>
> Am I doing something wrong or missing something?

Also let me add I have these settings in the config file:

ENABLE_SOAP = True
ENABLE_WEB_SERVER = True

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxx.edu 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/