atlas-connect-l AT lists.bnl.gov
Subject: Atlas-connect-l mailing list
List archive
Re: [Atlas-connect-l] No machines on ATLAS Connect condor pool?
- From: Lincoln Bryant <lincolnb AT uchicago.edu>
- To: Matthew Epland <matthew.epland AT cern.ch>, "atlas-connect-l AT lists.bnl.gov" <atlas-connect-l AT lists.bnl.gov>
- Subject: Re: [Atlas-connect-l] No machines on ATLAS Connect condor pool?
- Date: Thu, 15 Nov 2018 17:44:45 +0000
Hi Matthew,
We use a load-driven system for creating condor workers dynamically
(glideins). Some should appear automatically shortly after you submit.
Let me take a look and see if something is jammed up!
--Lincoln
On Thu, 2018-11-15 at 12:41 -0500, Matthew Epland wrote:
> Hello,
>
> I'm trying to launch some jobs from login but there appears to be no
> available slots at all on the cluster. All my jobs are in idle and it
> doesn't look like anyone is running other jobs online looking at the
> dashboard. I'm sure it's a bug, just not where.
>
> Thanks,
> Matt
>
> [mepland@login MBJ_HistFitter]$ condor_q -better-analyze
>
> -- Schedd: login.usatlas.org : <192.170.231.50:9618?...
> The Requirements expression for job 387936.000 is
>
> ( TARGET.Arch == "X86_64" ) && ( TARGET.OpSys == "LINUX" ) && (
> TARGET.Disk >= RequestDisk ) && ( TARGET.Memory >= RequestMemory ) &&
> ( TARGET.HasFileTransfer )
>
> Job 387936.000 defines the following attributes:
>
> DiskUsage = 100000
> ImageSize = 2
> RequestDisk = DiskUsage
> RequestMemory = ifthenelse(MemoryUsage =!=
> undefined,MemoryUsage,( ImageSize + 1023 ) / 1024)
>
> The Requirements expression for job 387936.000 reduces to these
> conditions:
>
> Slots
> Step Matched Condition
> ----- -------- ---------
> [0] 0 TARGET.Arch == "X86_64"
> [1] 0 TARGET.OpSys == "LINUX"
> [3] 0 TARGET.Disk >= RequestDisk
> [5] 0 TARGET.Memory >= RequestMemory
> [7] 0 TARGET.HasFileTransfer
>
> No successful match recorded.
> Last failed match: Thu Nov 15 11:28:05 2018
>
> Reason for last match failure: no match found
>
> 387936.000: Run analysis summary ignoring user priority. Of 0
> machines,
> 0 are rejected by your job's requirements
> 0 reject your job because of their own requirements
> 0 match and are already running your jobs
> 0 match but are serving other users
> 0 are available to run your job
>
> WARNING: Be advised:
> No machines matched the jobs's constraints
> [mepland@login MBJ_HistFitter]$ condor_status
> [mepland@login MBJ_HistFitter]$ condor_q
>
>
> -- Schedd: login.usatlas.org : <192.170.231.50:9618?... @ 11/15/18
> 11:30:17
> OWNER BATCH_NAME SUBMITTED DONE RUN IDLE TOTAL
> JOB_IDS
> mepland CMD: condor_job.sh 11/15 11:27 _ _ 115 115
> 387936.0-114
>
> 115 jobs; 0 completed, 0 removed, 115 idle, 0 running, 0 held, 0
> suspended
> [mepland@login MBJ_HistFitter]$ condor_status -debug
> [mepland@login MBJ_HistFitter]$ condor_status -avail
> [mepland@login MBJ_HistFitter]$
>
> --
> Matthew Epland
> Duke University Department of Physics
> matthew.epland AT cern.ch
>
> _______________________________________________
> Atlas-connect-l mailing list
> Atlas-connect-l AT lists.bnl.gov
> https://lists.bnl.gov/mailman/listinfo/atlas-connect-l
-
[Atlas-connect-l] No machines on ATLAS Connect condor pool?,
Matthew Epland, 11/15/2018
-
Re: [Atlas-connect-l] No machines on ATLAS Connect condor pool?,
Lincoln Bryant, 11/15/2018
- Re: [Atlas-connect-l] No machines on ATLAS Connect condor pool?, Lincoln Bryant, 11/15/2018
-
Re: [Atlas-connect-l] No machines on ATLAS Connect condor pool?,
Lincoln Bryant, 11/15/2018
Archive powered by MHonArc 2.6.24.