Re: [Condor-users] Job requirements not satisfied even when Requirements = TRUE

["Koller, Garrett" <kollerg14@xxxxxxxxxxxx>]

Mr. Cafaro,

Sure, that's easy.  Just run 'condor_status -long | grep ^IsValidCheckpointPlatform' to see the expression that defines the value for "IsValidCheckpointPlatform".  The expression depends a lot on the job being submitted.  Because of this, note that in this expression "MY.*" refers to a variable in the machine's ClassAd (will be listed in 'condor_status -long') and "TARGET.*" refers to a variable in the job's ClassAd (will be listed in 'condor_q -long').

Best Regards,
 ~ Garrett K.
Washington and Lee University
condor.cs.wlu.edu

On Aug 31, 2011, at 9:51 PM, Mark Cafaro wrote:

> Hi Garrett,
> 
> I have investigated this possibility and found it is likely not causing our problem. Requirements is appended, 
> but I can overwrite the appended requirements with condor_qedit. In either case, I would not expect a match 
> to be made if the manager wasn't able to match the requirements with the node. The manager matchs, but 
> the node refuses.
> 
> I am wondering if this doesn't have to do with the fact that the node has:
> 
> Requirements = ( START ) && ( IsValidCheckpointPlatform )
> 
> I can't be sure that isValidCheckpointPlatform evaluates to true on my platform. Is there any way to determine
> this?
> 
> On Aug 31, 2011, at 6:37 PM, Koller, Garrett wrote:
> 
>> Mr. Cafaro,
>> 
>> The job's requirements expression is probably being appended to after it is submitted.  Usually, the requirements in the submission file are logically and-ed (&&) with an expression that says what the job needs from its execution machine in terms of file transfer.  When the job is in the queue, run something like 'condor_q -long <Job_Cluster_ID> | grep -i ^Requirements', where <Job_Cluster_ID> is the ID for the job you just submitted.  There you will see the Requirement expression in its entirety.  Most likely, you are asking Condor to do a file transfer mechanism that isn't supported by your environment.  See Section 2.5.4, "Submitting Jobs Without a Shared File System: Condor’s File Transfer Mechanism," in the Condor manual (7.6.1 for me) for more information and note when it talks about "FileSystemDomain" and the like as this is one of the things appended to the job's Requirements expression depending on the type of file transfer desired.
>> 
>> Best Regards,
>> ~ Garrett K.
>> Washington and Lee University
>> condor.cs.wlu.edu
>> 
>> On Aug 31, 2011, at 9:18 PM, Mark Cafaro wrote:
>> 
>>> I am submitting sh_loop.cmd (from the condor examples) to my manager. It matches with a node and sends the job off. The node, however, refuses to accept the job claiming "Job requirements not satisfied.". 
>>> 
>>> The job is set with Requirements = TRUE. How can requirements not be satisfied and how can a match be made if the requirements were not satisfied?
>>> _______________________________________________
>>> 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/