Re: [Condor-users] Why does machine reject job for unknown reasons

["Alexander Dietz" <Alexander.Dietz@xxxxxxxxxxxxxx>]

Hi,

thanks for the quick reply, but this problem is not related to some network issues; I am submitting the DAG directly on the condor-pool. The jobs evetually gets executed on the pool, but the time until this happens can be really large (~hours).

Also, where can I find the log files to look for whats going on?

Thanks
  Alex

On 5/15/07, Johan Bengtsson < johan.bengtsson@xxxxxxxxxxxxx> wrote:

On tis, 2007-05-15 at 14:53 +0100, Alexander Dietz wrote:
> Hi,
>
> sorry to bother you again with my question, but this problem still
> persists. I have recieved so far no idea how to find out why
> condor-jobs are rejected ...

Hi Alex,
Have you checked that both forward and backward name resolving works for
the machines in your cluster? I think that every time this problem has
occured in my pool, name resolution has been the cause.

        / Johan


> Cheers
>   Alex
>
> On 5/14/07, Alexander Dietz <Alexander.Dietz@xxxxxxxxxxxxxx> wrote:
>         Hi,
>
>         thanks for this suggestion, but the output really does not
>         help me further (see below). It looks like that 150 machine
>         are good to run the jobs on, but still they are rejected for
>         unknown reasons! I need them to start immediately because of a
>         timely limited online-demonstration for the work I am doing.
>         Any other suggestions?
>
>         Cheers
>           Alex
>
>         > condor_q -better-analyze 1082109.0
>
>         1082109.000:  Run analysis summary.  Of 152 machines,
>               2 are rejected by your job's requirements
>               0 reject your job because of their own requirements
>               0 match but are serving users with a better priority in
>         the pool
>             150 match but reject the job for unknown reasons
>               0 match but will not currently preempt their existing
>         job
>               0 are available to run your job
>
>         The Requirements _expression_ for your job is:
>
>         ( target.Arch == "X86_64" ) && ( target.OpSys == "LINUX" ) &&
>         ( ( target.CkptArch == target.Arch ) || ( target.CkptArch is
>         undefined ) ) &&
>         ( ( target.CkptOpSys == target.OpSys ) || ( target.CkptOpSys
>         is undefined ) ) &&
>         ( target.Disk >= DiskUsage ) && ( ( target.Memory * 1024 ) >=
>         ImageSize )
>
>             Condition                         Machines Matched
>         Suggestion
>             ---------                         ----------------
>         ----------
>         1   ( target.Disk >= 10000 )          150
>         2   ( target.Arch == "X86_64" )       152
>         3   ( target.OpSys == "LINUX" )       152
>         4   ( ( target.CkptArch == target.Arch ) || ( target.CkptArch
>         is undefined ) )
>                                               152
>         5   ( ( target.CkptOpSys == target.OpSys ) ||
>         ( target.CkptOpSys is undefined ) )
>                                               152
>         6   ( ( 1024 * target.Memory ) >= 10000 )152
>
>
>
>
>
>         On 5/14/07, Ian Chesal <ian.chesal@xxxxxxxxx> wrote:
>
>
>                 On 5/14/07, Alexander Dietz
>                 <Alexander.Dietz@xxxxxxxxxxxxxx> wrote:
>                         Hi,
>
>                         I have a problems when sumbitting a DAG to
>                         condor; before any of the jobs gets executed
>                         they are rejected for unknown reasons, like
>                         the following messages suggest:
>
>                         > condor_q -analyze 1076700.0
>
>                 Alex,
>
>                 If you're running 6.8.x on Linux you can use the
>                 -better-analyze option which is infinitely more
>                 helpful than -analyze:
>
>                 condor_q -better-analyze 1076700.0
>
>                 - Ian
>
>
>
>
>                 _______________________________________________
>                 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 either
>                 https://lists.cs.wisc.edu/archive/condor-users/
>                 http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR
>
>
> _______________________________________________
> 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 either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR

_______________________________________________
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 either
https://lists.cs.wisc.edu/archive/condor-users/
http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR