To be more clear, the jobs aren't starting due to the group being at their
limit, which is normal. But slurm is spamming that error to the log file for
every job that is at a particular GrpTRESRunLimit which is not normal.
Other than the log being littered with incorrect error messages, things
On 1/31/19 8:12 AM, Christopher Benjamin Coffey wrote:
This seems to be related to jobs that can't start due to in our case:
AssocGrpMemRunMinutes, and AssocGrpCPURunMinutesLimit
Must be a bug relating to GrpTRESRunLimit it seems.
Do you mean can't start due to not enough time, or can't star
Hi All,
This seems to be related to jobs that can't start due to in our case:
AssocGrpMemRunMinutes, and AssocGrpCPURunMinutesLimit
Must be a bug relating to GrpTRESRunLimit it seems.
Best,
Chris
—
Christopher Coffey
High-Performance Computing
Northern Arizona University
928-523-1167
On 1
Hi, we upgraded to 18.08.5 this morning and are seeing odd errors in the
slurmctld logs:
[2019-01-31T08:24:13.684] error: select_nodes: calling _get_req_features() for
JobId=16599048 with not NULL job resources
[2019-01-31T08:24:13.685] error: select_nodes: calling _get_req_features() for
JobId
