On 7/11/18 2:44 pm, Brian Andrus wrote:
Ah just scontrol reconfigure doesn't actually make it take effect.
Restarting slurmctld did it.
Phew! Glad to hear that's sorted out.. :-)
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
Ah. I thought I had set that.
So I did and now it is:
AccountingStorageEnforce = associations,limits
But I am still able to request and get resources on cluster3 using projectA
as my account..
Heck, I just tried using a fake account (account=asdas) and it worked...
"That ain't right..." - Guy
Ah just scontrol reconfigure doesn't actually make it take effect.
Restarting slurmctld did it.
On Tue, Nov 6, 2018 at 7:07 PM Christopher Samuel wrote:
> On 7/11/18 1:57 pm, Brian Andrus wrote:
>
> > Ah. I thought I had set that.
> > So I did and now it is:
> > AccountingStorageEnforce =
Hmm. ok, so using unmatched accounts makes a fail:
(on cluster1)
$ srun -n16 -A Prod--pty bash
*srun: error: Unable to allocate resources: Invalid account or
account/partition combination specified*
But using a valid account also fails:
$ srun -n16 -A projectA --pty bash
*srun: error: Unable to
Hi Yair,
You can set maxsubmitjob=0 on an account.
The error message isn't helpful beyond the obvious though:
] salloc
salloc: error: AssocMaxSubmitJobLimit
salloc: error: Job submit/allocate failed: Job violates accounting/QOS policy
(job submit limit, user's size and/or time limits)
So
On 6/11/18 7:49 pm, Baker D.J. wrote:
The good new is that I am assured by SchedMD that the bug has been fixed
in v18.08.3.
Looks like it's fixed in this commmit.
commit 3d85c8f9240542d9e6dfb727244e75e449430aac
Author: Danny Auble
Date: Wed Oct 24 14:10:12 2018 -0600
Handle symbol
