[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] condor_store_cred failure



I tried to start the condor_schedd and this is the following error I am getting in the log

10/22 11:41:21 (pid:3816) Locale: English_United States.1252
10/22 11:41:21 (pid:3816) ******************************************************
10/22 11:41:21 (pid:3816) ** condor_schedd (CONDOR_SCHEDD) STARTING UP
10/22 11:41:21 (pid:3816) ** C:\condor\bin\condor_schedd.exe
10/22 11:41:21 (pid:3816) ** SubsystemInfo: name=SCHEDD type=SCHEDD(5) class=DAEMON(1)
10/22 11:41:21 (pid:3816) ** Configuration: subsystem:SCHEDD local:<NONE> class:DAEMON
10/22 11:41:21 (pid:3816) ** $CondorVersion: 7.4.4 Oct 13 2010 BuildID: 279383 $
10/22 11:41:21 (pid:3816) ** $CondorPlatform: INTEL-WINNT50 $
10/22 11:41:21 (pid:3816) ** PID = 3816
10/22 11:41:21 (pid:3816) ** Log last touched 10/21 12:21:44
10/22 11:41:21 (pid:3816) ******************************************************
10/22 11:41:21 (pid:3816) Using config source: C:\condor\condor_config
10/22 11:41:21 (pid:3816) Using local config sources: 
10/22 11:41:21 (pid:3816)    C:\condor/condor_config.local
10/22 11:41:21 (pid:3816) DaemonCore: Command Socket at <129.186.214.51:2626>
10/22 11:41:21 (pid:3816) History file rotation is enabled.
10/22 11:41:21 (pid:3816)   Maximum history file size is: 20971520 bytes
10/22 11:41:21 (pid:3816)   Number of rotated history files is: 2
10/22 11:41:21 (pid:3816) my_popen: CreateProcess failed
10/22 11:41:21 (pid:3816) Failed to execute C:\condor/bin/condor_shadow.std.exe, ignoring

Any additional information on how to fix this would be appreciated.

-Eric


Eric Fritz
Assistant Scientist II
Iowa State University
2255G Kildee Hall
Ames, IA 50014
________________________________________
From: condor-users-bounces@xxxxxxxxxxx [condor-users-bounces@xxxxxxxxxxx] On Behalf Of Sónia Liléo [sonia.lileo@xxxxx]
Sent: Friday, October 22, 2010 2:38 AM
To: 'Condor-Users Mail List'
Subject: Re: [Condor-users] condor_store_cred failure

Hi Eric,

I had the same problem before when setting up a condor pool on Windows machines.

I attach below the information I got from the condor-users concerning storing credentials when using Windows opsys.

Which operative system are you using?

Hope it helps,
Sónia

___________________________________________________________

Från: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] För Ian Chesal
Skickat: den 24 september 2010 14:01
Till: Condor-Users Mail List
Ämne: Re: [Condor-users] Condor_store_cred - Setting up Condor on Windows

Sonia,

You'll need to start a schedd deamon on your execute node, run the credential store command, and then shut down the schedd. It's a necessity of storing credentials. It only has to be running while you're storing credentials.

- Ian

__________________________________________________________________________________________

On 2010-09-24, at 5:41 AM, Sónia Liléo <sonia.lileo@xxxxx> wrote:
Hi Condor-Users!


I have written about this before and I will write about it again because I am still stumbling on this issue.

I am using a software that requires that Condor always use the same user account when running jobs. Right now I have a small Condor pool with 3 machines running Windows.

I have defined in the condor_config file of each machine SLOT1_USER = domain\user_account that Condor should use to run the jobs.
I have also included DEDICATED_EXECUTE_ACCOUNT_REGEXP = True.

But the problem occurs when I have to store the credentials on each machine.
I have received instructions from my software supplier that I should run CONDOR_STORE_CRED ADD on every machine of the pool.

But when I issue the command CONDOR_STORE_CRED ADD I get the error "Make sure your ALLOW_WRITE setting includes this host". And, yes, it does. The ALLOW_WRITE variable includes this host (it is set to *).

When the software supplier contacted the Condor Team regarding this issue they got the following answer,

This is a common problem people encounter when setting up Condor on Windows. This error indicates that there is a communication problem between the condor_store_cred tool and the condor_schedd daemon. The first thing you want to do is verify that the schedd is in fact running on the machine from which you are executing condor_store_cred. If it is, the SchedLog is the place to look for details on why the communication is failing. A common reason is because of a misconfigured security setup, which is why the error message refers to HOSTALLOW_WRITE. Of course, there may be other problems. Adding the D_SECURITY flag to the SCHEDD_DEBUG configuration macro will allow you to get the most information out of your SchedLog.

Hope this helps. Let me know if you need any more help tracking this down.

Thanks,
Greg Quinn
Condor Team

Greg wrote that
The first thing you want to do is verify that the schedd is in fact running on the machine from which you are executing condor_store_cred.
I have checked it, and no, schedd daemon is not running on the machine I am executing condor_store_cred. It is only running on the central manager. And there the command condor_store_cred worked fine.

Isn't it so that condor_schedd should only run on the machine where the jobs may be submitted from, in my case this is the central manager?

1.       Is it really necessary to execute condor_store_cred add on every machine of my pool?

2.       If yes, is it necessary that condor_schedd runs on every machine of the condor pool?

3.       If yes, how should I do so that condor_schedd runs on every machine?


I include below the SchedLog file related to the submitted job with ID 29.
10.110.44.12 is the central manager where the jobs are submitted from; Condor_schedd is running on this machine; Condor_store_cred add worked fine on this machine.
10.110.44.19 is the execute machine; Condor_store_cred add didn't work on this machine; Condor_schedd is not running on this machine.

Any clue of what is happening?

Cheers,
Sónia

-----Ursprungligt meddelande-----
Från: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] För Fritz, Eric R [AN S]
Skickat: den 21 oktober 2010 21:16
Till: condor-users@xxxxxxxxxxx
Ämne: [Condor-users] condor_store_cred failure

Hello,

I am working on setting up a pool and I have a computer that is the manager set up and running and I'm trying to connect a 2nd computer to the pool and I can find the host on the user computer. But when I try to use condor_store_cred it tells me Operation failed, please make sure your allow_write setting includes this host. My allow write setting allows *.ans.iastate.edu so any computer in this domain. I have also tried putting in the full computer name and IP address but it still tells me the same thing. Whatever I do, the user computer will now be allowed write privileges. Any help would be great. Thanks.

-Eric


Eric Fritz
Assistant Scientist II
Iowa State University
2255G Kildee Hall
Ames, IA 50014
_______________________________________________
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/