Thanks Daniela, Sam, Stephen. The reason for "no compatible resources"
is to be found in one of your suggestions - in this case. It turned out
to be lack of Production status in the CE, as the build script had been
tested but not subsequently amended. Thus it was marked “Special”.
Cheers for that – it's working now.
But there was another issue. There are a few possibilities that make "no
compatible resources" arise, and it is expensive for each admin to chase
them down independently. There are the SAM and Nagios tests, other tests
and real work. As you say, each of these can have various different
withheld reasons for "no compatible resources".
I'm asking if the desired resources of a job can be made explicit in a
way that helps the admin to determine precisely which CE resources he
needs to supply at his site. This also helps users. Without that, it
resolves to googling and guesswork.
Steve
|