Difference between revisions of "Known Errors and Workarounds - for Admins!"

From HPC users
Jump to navigationJump to search
(Created page with "== SLURM Errors == * When trying to submit a job, the following error message occures: sbatch: error: Batch job submission failed: Invalid account or account/partition combin...")
 
Line 3: Line 3:
  sbatch: error: Batch job submission failed: Invalid account or account/partition combination specified
  sbatch: error: Batch job submission failed: Invalid account or account/partition combination specified
** Three steps: Delete the account within slurm, add it afterwards and set the default workgroup account:
** Three steps: Delete the account within slurm, add it afterwards and set the default workgroup account:
  sacctmgr delete user name=abcd1234 account=agoldprim
  sacctmgr delete user name=abcd1234 account=agtestgroup
   
  sacctmgr add user name=abcd1234 account=agtestgroup
** Reason: The SLURM manager doesn't connect the user account to the standard work group when jos are submitted.
sacctmgr modify user where name=abcd1234 set defaultaccount=agtestgroup
Technically this could be bypassed by adding account=ag<workgroup> when submitting the jobs.
 
** Reason: The SLURM manager doesn't connect the user account to the standard work group properly when jobs are submitted. <br/> Technically this could be bypassed by adding account=ag<workgroup> when submitting the jobs.

Revision as of 14:10, 4 November 2019

SLURM Errors

  • When trying to submit a job, the following error message occures:
sbatch: error: Batch job submission failed: Invalid account or account/partition combination specified
    • Three steps: Delete the account within slurm, add it afterwards and set the default workgroup account:
sacctmgr delete user name=abcd1234 account=agtestgroup
sacctmgr add user name=abcd1234 account=agtestgroup
sacctmgr modify user where name=abcd1234 set defaultaccount=agtestgroup
 
    • Reason: The SLURM manager doesn't connect the user account to the standard work group properly when jobs are submitted.
      Technically this could be bypassed by adding account=ag<workgroup> when submitting the jobs.