Ah. I was getting ahead of myself. I used 'limits' and I have no limits
configured, only associations.
Changed it to just associations and all is good.
On Tue, Nov 6, 2018 at 8:34 PM Brian Andrus wrote:
> Hmm. ok, so using unmatched accounts makes a fail:
> (on cluster1)
> $ srun -n16 -A Prod--
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 a
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 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 = associ
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 = 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
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 Fle
On 7/11/18 7:35 am, Brian Andrus wrote:
I am able to submit using account=projectB on cluster3. ???
Since 'projectB' is a child of account ' DevOps', which is only
associated with cluster1 and cluster2, shouldn't I be denied the ability
to run using that accout on cluster3?
What does this sa
All,
Ok, I set up a few clusters in slurmdb. They are not federated.
I set up some accounts too. One primary for each cluster, plus a few child
accounts (project codes)
Something like:
sacctmgr add account DevOps Cluster=cluster1,cluster2
sacctmgr -add account projectA Parent=DevOps
sacctmgr -add
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 th
Thanks for this. We'll try the workaround script. It is not mission-critical
but our users have gotten accustomed to seeing these metrics at the end of each
run and its nice to have. We are currently doing this in a test VM environment,
so by the time we actually do the upgrade to the cluster pe
But isn't that a user association setting and not an account setting? So
I would have to set it for every user/default account association, no?
Technically doable, but definitely more difficult to manage.
Brian Andrus
On 11/6/2018 3:58 AM, Yair Yarom wrote:
Hi,
You can set the maxsubmitjob=
Hello,
I hope this is a quick question.
The way I read the man page (srun/sbatch), I should be allowed a request like
--constraint="broadwell|haswell"
to get either a broadwell or a haswell node, or not? (I mean yes, assuming
nodes with that feature exists).
I can't get that to work; when I t
Hi,
You can set the maxsubmitjob=0 on that default account. That should prevent
anyone from using it, but it won't have a specific message like with the
lua plugin. E.g.
sacctmgr update account default set maxsubmitjob=0
Regards,
Yair.
On Tue, Nov 6, 2018 at 12:58 AM Renfro, Michael wrote:
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 res
Hello Mike et al,
This is a known bug in slurm v18.08*. We installed the initial release a short
while ago and came across this issue very quickly. We actually use this script
at the end of the job epilog to report job efficiency to users, and so it is
real shame that it is now broken! The goo
15 matches
Mail list logo
