If you see this error:
$ sbatch myjob.sh sbatch: error: AssocMaxSubmitJobLimit sbatch: error: Batch job submission failed: Job violates accounting/QOS policy (job submit limit, user's size and/or time limits) $
This indicates that you did not submit your job with the –account= parameter, and Slurm has attempted to use your default account code. Every Slurm user on Comet has the allusers account as their default and this has no permissions to submit jobs.
–account=
You must use the account code of an actual HPC Project you are a member of; this is effectively the same as the name of one of your unix groups on Comet.
The following error:
$ sbatch df.sbatch sbatch: error: Batch job submission failed: Invalid account or account/partition combination specified $
This indicates that the account code you submitted does not have permission to submit jobs to the partition you specified. The most common cause for this is using the account code of a non-funded HPC Project (or a funded project with zero/negative balance) against a paid partition (those are the partitions ending in _paid).
_paid
Unfunded projects (or zero/negative balance funded projects) may only access free partitions (those ending in _free), as listed on the Comet HPC Resources page.
_free
More details about free/paid partitions and billing policies can be found in our Billing & Project Funds section.
Only account codes of funded projects which have a positive balance may submit jobs against paid partitions. If you have a funded HPC Project, you can check your project balance on the finance tab of the management page of your project. All projects can be found under My HPC Projects.
Back to FAQ index
Table of Contents
Main Content Sections
Documentation Tools