[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Linux scheduler authentication problem
- Date: Fri, 22 Oct 2010 09:34:49 -0400
- From: Ian Chesal <ichesal@xxxxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Linux scheduler authentication problem
All your machines need to have CLAIMTOBE in their list of authentication methods for this to work.
On 2010-10-22, at 4:56 AM, Horvátth Szabolcs <szabolcs@xxxxxxxxxxxxx> wrote:
> I'd like to replace our windows scheduler machine with a linux one, and we're having some authentication problems when submitting jobs.
> This is what I get in the SchedLog file after a job submission (using fulldebug mode):
> 10/22 10:47:21 Adding to resolved authorization table: */192.168.0.71: READ
> 10/22 10:47:21 Received TCP command 1111 (QMGMT_CMD) from <192.168.0.71:2281>, access level READ
> 10/22 10:47:21 AUTHENTICATE: no available authentication methods succeeded, failing!
> 10/22 10:47:21 SCHEDD: authentication failed: AUTHENTICATE:1003:Failed to authenticate with any method
> 10/22 10:47:21 condor_read(): Socket closed when trying to read 5 bytes from <192.168.0.71:2281>
> 10/22 10:47:21 IO: EOF reading packet header
> 10/22 10:47:21 QMGR Connection closed
> And this is what condor submit reports:
> ERROR: Failed to connect to queue manager condormaster.digicpictures.local
> AUTHENTICATE:1003:Failed to authenticate with any method
> I tried to add 'SEC_DEFAULT_AUTHENTICATION_METHODS = ClaimToBe' to the condor_config file based on an earlier post found in the archives but did not help much.
> (It would be no problem turning off any authentication since this is a closed network.)
> Thanks for any tips, I'm pretty much lost in linux authentication land.
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: