Re: [Condor-users] Fix for the possibly bogus "ceiling(ifThenElse(JobVMMemory ..." requirement issue

[Kevin.Buckley@xxxxxxxxxxxxx]

> Whist the Condor compute nodes seem to start up fine, removing
> some problems that had been seen before on the win7 platform,
> even the simplest of jobs, pass a .BAT file over and run it,
> seem to fail to find  a host, because, so condor_q -better_analyze
> suggests of this:
>
>     Condition                         Machines Matched    Suggestion
>     ---------                         ----------------    ----------
> 1   ( ( 1024 * ceiling(ifThenElse(JobVMMemory isnt
> undefined,JobVMMemory,9.765625000000000E-04)) ) >= 1 )
>                                       0                   REMOVE

It turns out that the above "Condition" was not what was stopping
tasks from running on the node in question, so in case it sheds
(scheds?) any light in why that condition appears in the first
place, the issue here was that the /master/submit host/ had been
left out of the ALLOW_WRITE specification and was thus failing to
achieve the

  command 442 (REQUEST_CLAIM)

on the compute node as it tried to move from "Matched" to "Claimed".

Is that likely to be one of the causes of the "Condition" appearing ?

-- 
Kevin M. Buckley                                  Room:  CO327
School of Engineering and                         Phone: +64 4 463 5971
 Computer Science
Victoria University of Wellington
New Zealand