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

Re: [Condor-users] setting up condor pool



That seems to kind of work.

ld-chhfe02:/home/spervez1/condor.ld-chhfe02 $ bin/condor_config_val -master -rset "filenames = 2"
Successfully set configuration "FILENAMES = 2" on master ld-chhfe02.citadelgroup.com <10.32.242.23:63311>.
ld-chhfe02:/home/spervez1/condor.ld-chhfe02 $ sbin/condor_reconfig
Sent "Reconfig" command to local master
ld-chhfe02:/home/spervez1/condor.ld-chhfe02 $ bin/condor_config_val -master filenames
2

So it looks like everything is OK here. I then try this

ld-chhfe01:/home/spervez1/temp $ ~/condor.ld-chhfe01/bin/condor_status -const 'filenames == "2"'
ld-chhfe01:/home/spervez1/temp $ ~/condor.ld-chhfe01/bin/condor_status -const 'filenames == "1"'
ld-chhfe01:/home/spervez1/temp $ ~/condor.ld-chhfe01/bin/condor_status -const 'filenames == "1"'

Does this mean none of the machines are advertising this in their classads?

I also tried adding this to my submit file

Requirements = Filenames=="2"

And the jobs just seem to sit there with no match.

Salman


-----Original Message-----
From: Matthew Farrellee [mailto:matt@xxxxxxxxxx]
Sent: Wednesday, February 15, 2012 1:30 PM
To: Condor-Users Mail List
Cc: Pervez, Salman
Subject: Re: [Condor-users] setting up condor pool

man condor_config_val -

  Any changes made by condor_config_val will not take effect  until  con-
  dor_reconfig is invoked.

Best,


matt

On 02/15/2012 02:26 PM, Pervez, Salman wrote:
> Hmmm...I'm not exactly sure what happened. But things to be working fine now. I removed some of the .out and .error files (for the simple.cpp example) which may have made a difference, although I can't imagine why. But I can execute jobs on my cluster which is great. Here's my next issue... :)
>
> I'd like to set custom parameters for the classad of each machine. So I modified my global config file to change these values.
>
> ENABLE_RUNTIME_CONFIG = true
> ALLOW_CONFIG = *
> SETTABLE_ATTRS_CONFIG = *
> SETTABLE_ATTRS_OWNER = filenames
>
> I then restarted all my condor daemons and tried this...
>
> ld-chhfe01:/home/spervez1/condor.ld-chhfe01 $ bin/condor_config_val -rset "filenames:1"
> Successfully set configuration "FILENAMES:1" on master ld-chhfe01.citadelgroup.com<10.32.242.22:62373>.
> ld-chhfe01:/home/spervez1/condor.ld-chhfe01 $ bin/condor_config_val filenames   Not defined: FILENAMES
>
> What happened?
>
> Salman
>
> -----Original Message-----
> From: Matthew Farrellee [mailto:matt@xxxxxxxxxx]
> Sent: Wednesday, February 15, 2012 12:53 PM
> To: Condor-Users Mail List
> Cc: Pervez, Salman
> Subject: Re: [Condor-users] setting up condor pool
>
> Chances are high it's a FILESYSTEM_DOMAIN and file transfer default issue.
>
> http://spinningmatt.wordpress.com/2011/06/12/getting-started-creating-a-multiple-node-condor-pool/
>
> Best,
>
>
> matt
>
> On 02/15/2012 01:23 PM, Pervez, Salman wrote:
>> Great, I've got a condor pool now. I tried submitting some jobs to it, and they don't seem to be executing. Condor_q just shows their status as submitted. This was not the case when I had a 1 machine pool. The jobs would execute right away. Any idea why there is a delay here? Or where I might look?
>>
>> Salman
>>
>> -----Original Message-----
>> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Thomas Luff
>> Sent: Wednesday, February 15, 2012 11:53 AM
>> To: Condor-Users Mail List
>> Subject: Re: [Condor-users] setting up condor pool
>>
>> You need to set the CONDOR_HOST attribute in your condor_config file.
>>
>> As this is going to be the same for all machines in your pool you want to set this value the global config file and not the local file.
>>
>> Once this is done you might find that your machines are not allowed to talk to each other because of condor's default host authorization. This is a basic authorization used by condor to control access based on hostnames. To make sure everything is running just allow read/write to anyone.
>>
>> ALLOW_READ = *
>> ALLOW_WRITE= *
>> ALLOW_NEGOTIATOR = $(CONDOR_HOST)
>>
>> Then you can go back later and fine tune the host authorization or switch to a more secure method.
>>
>> ________________________________________
>> From: condor-users-bounces@xxxxxxxxxxx [condor-users-bounces@xxxxxxxxxxx] On Behalf Of Pervez, Salman [Salman.Pervez@xxxxxxxxxxxxxxxx]
>> Sent: 15 February 2012 17:10
>> To: condor-users
>> Subject: [Condor-users] setting up condor pool
>>
>> Hi everyone, thanks for all the help so far (Thomas!). I can now start up Condor daemons on 3 of my machines which is great. The problem is they don't seem to know about each other. Which made me realize that I never actually told my execute machines how to get in touch with the master. Can someone tell me how to do this? I have a master set up as a submit machine and two others that are just execute machines. Appreciate the input. Thanks!
>>
>> Salman
>>
>> -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.
>>
>> _______________________________________________
>> 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/
>
> _______________________________________________
> 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/



CONFIDENTIALITY AND SECURITY NOTICE

The contents of this message and any attachments may be confidential and proprietary and also may be covered by the Electronic Communications Privacy Act. This message is not intended to be used by, and should not be relied upon in any way, by any third party.  If you are not an intended recipient, please inform the sender of the transmission error and delete this message immediately without reading, disseminating, distributing or copying the contents. Citadel makes no assurances that this e-mail and any attachments are free of viruses and other harmful code.