Submitting a job without specifying the proper shell will return a warning like below:
sbatch: WARNING: Job script lacks first line beginning with #! shell. Injecting '#!/bin/bash' as first line of job script.
If an error is encountered, the job is rejected.
Not specifying a project account
It is required to specify an account for a job to run. Please use the
--account=<project-code> option to do this.
sbatch: error: ERROR: Job invalid: Must specify account for job sbatch: error: Job submit/allocate failed: Unspecified error
Incorrrect resource configuration
If one makes a request for a node that doesn't exist, the job is rejected.
salloc: error: Job submit/allocate failed: Requested node configuration is not available
An example is requesting a regaular compute node, while also requesting a larger amount of memory than a compute node has.
Specify wrong account
If a user tries to set the
--account option with a project that they are not on, then the job is rejected.
sbatch: error: Job submit/allocate failed: Invalid account or account/partition combination specified
Using a restricted project in a slurm job
If a user submits a job and uses a project that is restricted, the following message will be shown and the job will not be submitted:
sbatch: error: AssocGrpSubmitJobsLimit sbatch: error: Batch job submission failed: Job violates accounting/QOS policy (job submit limit, user's size and/or time limits)
Leading whitespace in job name
Leading whitespace is not supported in SLURM job names. Your job will be rejected with an error message if you submit a job with a space in the job name:
sbatch: error: Invalid directive found in batch script: name
You can fix this by removing leading whitespace in the job name.
Script is empty or only contains whitespace
An empty file is not permitted to be submitted (included whitespace only files).
sbatch: error: Batch script is empty!
sbatch: error: Batch script contains only whitespace!