Re: [Condor-users] How to get detail in why a match was not found?

[Nick LeRoy <nleroy@xxxxxxxxxxx>]

On Tue April 15 2008, Finch, Ralph wrote:
> Still trying to debug a problem with 7.0.1 in a wintel pool, where if a
> submit job has a Requirements set it never finds a match.  I need more
> output in MatchLog than this:
>
> 4/15 16:54:45 (fd:4) (pid:1180)  Rejected 712.0 rfinch@water
> <32.179:1045>: no match found
> 4/15 16:54:45 (fd:4) (pid:1180)  Rejected 703.0 rfinch@water
> <32.179:1045>: no match found
> 4/15 16:54:45 (fd:4) (pid:1180)  Rejected 712.0 rfinch@water
> <32.179:1045>: no match found
>
> I really need output that will explain why a match was not found.  Which
> Requirement triggered a rejection?  I tried turning on all debugging
> with ALL_DEBUG = D_ALL but it didn't expand the info in MatchLog.

Try running 'condor_q -better'...  condor_q can look at the jobs in a queue 
(or specific jobs) and compare them to the existing machine ads, and can 
provide some human readable analysis of why the jobs aren't matching.

Note that not all platforms currently support '-better', in which case you'll 
be stuck with '-ana' (or, at least, not all did -- that might have changed, 
but I don't think so).

-Nick

-- 
           <<< It's the question that drives us. >>>
 /`-_    Nicholas R. LeRoy               The Condor Project
{     }/ http://www.cs.wisc.edu/~nleroy  http://www.cs.wisc.edu/condor
 \    /  nleroy@xxxxxxxxxxx              The University of Wisconsin
 |_*_|   608-265-5761                    Department of Computer Sciences