Re: [Condor-users] Make sure you have CONFIG access to the targetMaster.

["Alas, Alex [FEDI]" <aalas@xxxxxxxxxxxxx>]

I was able to set the password for my condor_pool@xxxxxxxxxx but I still
have the error message depicted above. I don't know which part of my
condor_config I should modify considering I went and double check the
cred setting in my host_cred and execute and summiting machines. But for
sure the pool's password was set on all the systems in my condor farm. 
I don't know if someone can 
>I am including the last entries of the masterlog from the system I'm
having problems with: 
11/12 17:28:11 ******************************************************
11/12 17:28:11 ** Condor (CONDOR_MASTER) STARTING UP
11/12 17:28:11 ** C:\Condor\bin\condor_master.exe
11/12 17:28:11 ** $CondorVersion: 6.8.8 Dec 19 2007 $
11/12 17:28:11 ** $CondorPlatform: INTEL-WINNT50 $
11/12 17:28:11 ** PID = 1664
11/12 17:28:11 ** Log last touched 11/12 17:27:35
11/12 17:28:11 ******************************************************
11/12 17:28:11 Using config source: C:\Condor\condor_config
11/12 17:28:11 Using local config sources: 
11/12 17:28:11    C:\Condor/condor_config.local
11/12 17:28:11 DaemonCore: Command Socket at <10.xxx.xxx.xx4:1038>
11/12 17:28:52 Started DaemonCore process
"C:\Condor/bin/condor_schedd.exe", pid and pgroup = 2324
11/12 17:28:52 Started DaemonCore process
"C:\Condor/bin/condor_startd.exe", pid and pgroup = 2336
11/12 17:28:52 Started DaemonCore process
"C:\Condor/bin/condor_credd.exe", pid and pgroup = 2376
11/12 17:28:58 attempt to connect to <10.xxx.xxx.xx6:9618> failed:
connect errno = 10061 connection refused.
11/12 17:28:58 ERROR: SECMAN:2003:TCP connection to
<10.xxx.xxx.xx6:9618> failed

11/12 17:28:58 Failed to start non-blocking update to
<10.xxx.xxx.xx6:9618>.
11/12 17:33:58 attempt to connect to <10.xxx.xxx.xx6:9618> failed:
connect errno = 10061 connection refused.
11/12 17:33:58 ERROR: SECMAN:2003:TCP connection to
<10.xxx.xxx.xx6:9618> failed

11/12 17:33:58 Failed to start non-blocking update to
<10.xxx.xxx.xx6:9618>.

>These are the last entries on the Masterlog for the Cred_host and
central manager. (The 10.xxx.xxx.xx6:9618 is the IP for the
Host_cred\Central Manager machine)
11/12 16:29:04 **** Condor (condor_MASTER) EXITING WITH STATUS 0
11/12 16:30:23 ******************************************************
11/12 16:30:23 ** Condor (CONDOR_MASTER) STARTING UP
11/12 16:30:23 ** C:\condor\bin\condor_master.exe
11/12 16:30:23 ** $CondorVersion: 6.8.7 Nov 29 2007 $
11/12 16:30:23 ** $CondorPlatform: INTEL-WINNT50 $
11/12 16:30:23 ** PID = 1596
11/12 16:30:23 ** Log last touched 11/12 16:29:04
11/12 16:30:23 ******************************************************
11/12 16:30:23 Using config source: C:\condor\condor_config
11/12 16:30:23 Using local config sources: 
11/12 16:30:23    C:\condor/condor_config.local
11/12 16:30:23    C:\condor/condor_config.local.credd
11/12 16:30:23 DaemonCore: Command Socket at <10.xxx.xxx.xx6:1035>
11/12 16:40:11 WinFirewall: get_CurrentProfile failed: 0x800706d9
11/12 16:40:11 Started DaemonCore process
"C:\condor/bin/condor_collector.exe", pid and pgroup = 3280
11/12 16:40:12 Started DaemonCore process
"C:\condor/bin/condor_negotiator.exe", pid and pgroup = 3292
11/12 16:40:13 Started DaemonCore process
"C:\condor/bin/condor_schedd.exe", pid and pgroup = 3312
11/12 16:40:13 Started DaemonCore process
"C:\condor/bin/condor_startd.exe", pid and pgroup = 3320
11/12 16:40:15 Started DaemonCore process
"C:\condor/bin/condor_credd.exe", pid and pgroup = 3344
11/12 17:25:34 DaemonCore: Command received via UDP from host
<10.xxx.xxx.xx6:1339>
11/12 17:25:34 DaemonCore: received command 60000 (DC_RAISESIGNAL),
calling handler (HandleSigCommand())
11/12 17:25:34 Got SIGQUIT.  Performing fast shutdown.
11/12 17:25:34 Sent signal 3 to COLLECTOR (pid 3280)
11/12 17:25:34 Sent signal 3 to NEGOTIATOR (pid 3292)
11/12 17:25:34 Sent signal 3 to SCHEDD (pid 3312)
11/12 17:25:34 Sent signal 3 to STARTD (pid 3320)
11/12 17:25:34 sspi_client_auth(): Oops! ISC() returned -2146893055!
11/12 17:25:34 ERROR: SECMAN:2004:Failed to start a session to
<10.xxx.xxx.xx6:9620> with TCP|AUTHENTICATE:1005:Failed to securely
exchange session key
11/12 17:25:34 Send_Signal: ERROR Connect to <10.xxx.xxx.xx6:9620>
failed.
11/12 17:25:34 ERROR: failed to send signal 3 to pid 3344
11/12 17:25:35 DaemonCore: Command received via UDP from host
<10.xxx.xxx.xx6:1356>
11/12 17:25:35 DaemonCore: received command 60011 (DC_NOP), calling
handler (handle_nop())
11/12 17:25:35 The NEGOTIATOR (pid 3292) exited with status 0
11/12 17:25:35 DaemonCore: Command received via UDP from host
<10.xxx.xxx.xx6:1360>
11/12 17:25:35 DaemonCore: received command 60011 (DC_NOP), calling
handler (handle_nop())
11/12 17:25:35 The COLLECTOR (pid 3280) exited with status 0
11/12 17:25:35 DaemonCore: Command received via UDP from host
<10.xxx.xxx.xx6:1361>
11/12 17:25:35 DaemonCore: received command 60011 (DC_NOP), calling
handler (handle_nop())
11/12 17:25:35 The SCHEDD (pid 3312) exited with status 0
11/12 17:25:35 The STARTD (pid 3320) exited with status 0
11/12 17:27:42 ******************************************************
11/12 17:27:42 ** Condor (CONDOR_MASTER) STARTING UP
11/12 17:27:42 ** C:\condor\bin\condor_master.exe
11/12 17:27:42 ** $CondorVersion: 6.8.7 Nov 29 2007 $
11/12 17:27:42 ** $CondorPlatform: INTEL-WINNT50 $
11/12 17:27:42 ** PID = 1588
11/12 17:27:42 ** Log last touched 11/12 17:26:15
11/12 17:27:42 ******************************************************
11/12 17:27:42 Using config source: C:\condor\condor_config
11/12 17:27:42 Using local config sources: 
11/12 17:27:42    C:\condor/condor_config.local
11/12 17:27:42    C:\condor/condor_config.local.credd
11/12 17:27:42 DaemonCore: Command Socket at <10.xxx.xxx.xx6:1038>
11/12 17:37:44 WinFirewall: get_CurrentProfile failed: 0x800706d9
11/12 17:37:44 Started DaemonCore process
"C:\condor/bin/condor_collector.exe", pid and pgroup = 3456
11/12 17:37:45 Started DaemonCore process
"C:\condor/bin/condor_negotiator.exe", pid and pgroup = 3468
11/12 17:37:46 Started DaemonCore process
"C:\condor/bin/condor_schedd.exe", pid and pgroup = 3476
11/12 17:37:47 Started DaemonCore process
"C:\condor/bin/condor_startd.exe", pid and pgroup = 3488
11/12 17:37:47 Started DaemonCore process
"C:\condor/bin/condor_credd.exe", pid and pgroup = 3500

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ian D. Alderman
Sent: Wednesday, November 12, 2008 11:19 AM
To: Condor-Users Mail List
Subject: Re: [Condor-users] Make sure you have CONFIG access to the
targetMaster.


On Nov 12, 2008, at 9:04 AM, Alas, Alex [FEDI] wrote:

> Hello to all,
> I am trying to configure CredD for windows in my condor pool. So far  
> I only have 2 execute/submit computers and one central manager so in  
> total 3 systems in my condor pool. Following a tutorial I found from  
> Greg Quinn, I configured  CredD. My central manager is configured to  
> act as the CredD host. When I was trying to set the pool password, I  
> had a problem in one of the systems, the error coming back is the  
> subject of this e-mail: Make sure you have CONFIG access to the  
> target Master. When checking the Masterlog file I found other errors:
> 11/11 16:41:18 attempt to connect to <10.xxx.xx.xx6:9618> failed:  
> connect errno = 10061 connection refused
> Searching for the error messages, I found a post where they  
> recommend to use the following command: condor_config_val  
> COLLECTOR_HOST, when I ran it on the troubled computer, it came back  
> with the right system name: computername.domain.com
> At this point I don't know where and how to troubleshoot this issue,  
> if someone has any suggestions they are welcome,
> Thanks in advance for your help.
>
> Respectfully,
> Alex Alas
> Systems Administrator


Hi Alex,

I'm not sure exactly what tutorial you're working from but I think you  
may need to modify your config so that condor_store_cred can access  
condor_master.  If your configuration requires password  
authentication, but the pool password isn't set yet, the attempt to  
authenticate fails.

If this is the problem, one way of enabling this is to let interactive  
users authenticate using NTSSPI; another is to temporarily modify the  
authentication methods list to include FS until after you've set the  
password.

Let me know if you'd like more detail.

Cheers,

-Ian

--
===================================
Ian D. Alderman
cell: 608.217.9959
main: 888.292.5320

Cycle Computing, LLC
Leader in Condor Grid Solutions
Enterprise Condor Support and Management Tools

_______________________________________________
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/