Re: [Condor-users] Remote Scheduler Job Submission

[Erik Aronesty <erik@xxxxxxx>]

FS_REMOTE security is easiest if you have NFS.  Other than that the
PASSWORD authentication is probably best (cross platform, easy to
understand and install).

On Thu, May 5, 2011 at 5:18 PM, Natarajan, Senthil <senthil@xxxxxxxx> wrote:
> Hi,
> Do I need to have GSI security in place (by following this http://www.globus.org/toolkit/docs/development/4.1.3/admin/quickstart/q-first.html#q-security )in order to submit jobs to Remote Scheduler.
>
> I tried to setup GSI security using https://condor-wiki.cs.wisc.edu/index.cgi/wiki?p=WisdomGsiSetup , but it is not working I am getting this error
>
>>condor_status
> Error: communication error
> 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:7).  There is probably a problem with your credentials.  (Did you run grid-proxy-init?)
>
>
> It will be great if someone point out some documentation to setup Remote Job submission (by setting up proper authentication in place).
>
> Thanks,
> Senthil
>
> -----Original Message-----
> From: Matthew Farrellee [mailto:matt@xxxxxxxxxx]
> Sent: Wednesday, April 20, 2011 9:40 AM
> To: Natarajan, Senthil
> Cc: 'Condor-Users Mail List'
> Subject: Re: [Condor-users] Remote Scheduler Job Submission
>
> On 04/20/2011 09:36 AM, Natarajan, Senthil wrote:
>> I am not using GSI or any other authentication to submit jobs to condor_schedd, just the LDAP authentication to the Linux box where central manager runs. Once users are in central manager linux box, they can just submit job using condor_submit.
>>
>> I am having the same authentication on the execute node from where I try to submit jobs remotely to central manager condor_schedd. It looks like condor_schedd expects some authentication if the job is submitted from other than where condor_schedd daemon runs.
>
> It is far more likely that your local condor_submit are just succeeding
> with FS, i.e. no AUTHENTICATE:1004:Failed to authenticate using FS.
>
> If you are requiring authentication, for remote submission, you'll need
> to have a mechanism in place that works across the wire.
>
> Best,
>
>
> matt
>
>> -----Original Message-----
>> From: Matthew Farrellee [mailto:matt@xxxxxxxxxx]
>> Sent: Wednesday, April 20, 2011 9:22 AM
>> To: Natarajan, Senthil
>> Cc: 'Condor-Users Mail List'
>> Subject: Re: [Condor-users] Remote Scheduler Job Submission
>>
>> On 04/20/2011 09:16 AM, Natarajan, Senthil wrote:
>>> Thanks Matt.
>>>
>>> I did try using condor_submit command tool, like this
>>>
>>>> condor_submit -name "scheduler name" job1.cmd and also
>>>>
>>>> condor_submit -remote "scheduler name" job1.cmd
>>>
>>> But I am getting the authentication error as mentioned in the below original post.
>>>
>>> Do I need to setup special authentication?
>>
>> That's all configuration.
>>
>> You should try mirroring the security settings from the condor_schedd
>> machine, which may include CAs. I don't use GSI very often, but the
>> error message suggests maybe you didn't grid-proxy-init.
>>
>> Best,
>>
>>
>> matt
>>
>>> Thanks,
>>> Senthil
>>>
>>> -----Original Message-----
>>> From: Matthew Farrellee [mailto:matt@xxxxxxxxxx]
>>> Sent: Wednesday, April 20, 2011 9:11 AM
>>> To: Condor-Users Mail List
>>> Cc: Natarajan, Senthil
>>> Subject: Re: [Condor-users] Remote Scheduler Job Submission
>>>
>>> You don't even need those daemons, just the condor_submit command-line tool.
>>>
>>> Best,
>>>
>>>
>>> matt
>>>
>>> On 04/20/2011 09:08 AM, Natarajan, Senthil wrote:
>>>> Hi,
>>>>
>>>> Is it possible to submit jobs to remote scheduler (central manager) from
>>>> the node which runs only condor_master and condor_start daemons?
>>>>
>>>> Thanks,
>>>>
>>>> Senthil
>>>>
>>>> *From:*Natarajan, Senthil
>>>> *Sent:* Friday, April 15, 2011 12:13 PM
>>>> *To:* Condor-Users Mail List
>>>> *Subject:* Remote Scheduler Job Submission
>>>>
>>>> Hi,
>>>>
>>>> I am trying to submit a job from one of the execute node (running only
>>>> condor_master and condor_startd daemons) to central manager by
>>>>
>>>> condor_submit -name "scheduler name" job1.cmd and also
>>>>
>>>> condor_submit -remote "scheduler name" job1.cmd
>>>>
>>>> But I am getting this Authentication Error:
>>>>
>>>> Submitting job(s)
>>>>
>>>> ERROR: Failed to connect to queue manager xxxx.xxx.edu
>>>>
>>>> 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:45).
>>>> 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
>>>>
>>>> I don't want users to submit jobs to different schedulers that's why I
>>>> am not running the schedulers on the execute nodes. This is a special
>>>> scenario.
>>>>
>>>> Do I need to setup Globus CA etc... to authenticate remote scheduler job
>>>> submission? Or is there any other easy way to do this.
>>>>
>>>> Thanks,
>>>>
>>>> Senthil
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Condor-users mailing list
>>>> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
>>>> subject: Unsubscribe
>>>> You can also unsubscribe by visiting
>>>> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>>>>
>>>> The archives can be found at:
>>>> https://lists.cs.wisc.edu/archive/condor-users/
>>>
>>
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>