Re: [Condor-users] [Condor-devel] information regarding ticket 1264

["Timothy St. Clair" <tstclair@xxxxxxxxxx>]

Alexandre - 

	The point of interest in your master log is the following:

07/07 15:02:33 (fd:3) (pid:2064) HANDSHAKE: server replied (method = 0)
07/07 15:02:33 (fd:3) (pid:2064) AUTHENTICATE: no available
authentication methods succeeded, failing!
07/07 15:02:33 (fd:3) (pid:2064) CLOSE <172.17.7.223:4442> fd=780
07/07 15:02:33 (fd:3) (pid:2064) SECMAN: unable to create security
session to <172.17.7.223:9620> via TCP, failing.
07/07 15:02:33 (fd:3) (pid:2064) Send_Signal: Warning: could not send
signal 15 (SIGTERM) to pid 2360 (still alive)
07/07 15:02:33 (fd:3) (pid:2064) Destroying Daemon object:
07/07 15:02:33 (fd:3) (pid:2064) Type: 1 (any), Name: (null), Addr:
<172.17.7.223:9620>
07/07 15:02:33 (fd:3) (pid:2064) FullHost: (null), Host: (null), Pool:
(null), Port: 9620
07/07 15:02:33 (fd:3) (pid:2064) IsLocal: N, IdStr: daemon at
<172.17.7.223:9620>, Error: (null)
07/07 15:02:33 (fd:3) (pid:2064)  --- End of Daemon object info ---
07/07 15:02:33 (fd:3) (pid:2064) ERROR: failed to send signal 15 to pid
2360

	In looking through the handshake your credd is trying you auth with
only PASSWORD, but the master is responding with NTSSPI, KERBEROS which
is failing authentication b/c there are no matching auth methods.   

You may want to try changing your condor_config.local file to:
CREDD.SEC_DEFAULT_AUTHENTICATION_METHODS="NTSSPI,PASSWORD" and give that
a whirl.  

Cheers,
Tim




On Wed, 2010-07-07 at 15:12 +0200, Alexandre Fayolle wrote:
> On Tuesday 06 July 2010 17:00:01 Alexandre Fayolle wrote:
> > On Tuesday 06 July 2010 15:43:56 Timothy St. Clair wrote:
> > > Alexandre -
> > > 
> > > 	If you have the logs from both the credd and master during this
> > > 
> > > scenario it will likely be useful.  Please set D_ALL = D_FULLDEBUG prior
> > > to sending the logs.
> > 
> > Thanks a lot for the quick answer.
> > 
> > I'll do that and report back asap.
> 
> Attached are the logs from the Central Manager (in a zip file) and the 
> configuration files for my instance (mostly generated by the Windows installer 
> and reading the documentation about setting up CondorCredd on Windows). 
> 
> What I did in the test:
> 
> * net start condor
> * wait a little bit
> * net stop condor
> * wait a little bit
> * manual kill CondorCredd from task manager. 
> 
> Thanks a lot for any help on this issue. 
> 
>