I am a systems administrator for a computing cluster.
We have around 24 nodes available, recently adding a whole new updated cluster
with upgraded nodes.
We use an interactive node that will randomly select from our list of computing
nodes to complete the job. We would like to find a way to
For others potentially seeing this on mailing list search, yes, I needed
that, which of course required creating an account charge which I wasn't
using. So I ran
sacctmgr add account default_account
sacctmgr add -i user $user Accounts=default_account
with an appropriate looping around for $user
You will probably need to.
The way we handle it is that we add users when the first submit a job
via the job_submit.lua script. This way the database autopopulates with
active users.
-Paul Edmon-
On 10/3/23 9:01 AM, Davide DelVento wrote:
By increasing the slurmdbd verbosity level, I got
I’d probably default to OpenHPC just for the community around it, but I’ll also
note that TrinityX might not have had any commits in their GitHub for an
18-month period (unless I’m reading something wrong).
On Oct 3, 2023, at 5:51 AM, John Joseph wrote:
External Email Warning
This email
By increasing the slurmdbd verbosity level, I got additional information,
namely the following:
slurmdbd: error: couldn't get information for this user (null)(xx)
slurmdbd: debug: accounting_storage/as_mysql:
as_mysql_jobacct_process_get_jobs: User xx has no associations, and
is not
Dear All,
Good afternoon
I would like to install and study and administer HPC, as first step planning
to install one of the HPC. When I check the docs I can see OpenHPC and TrintyX
both of them have slurm in built
Like to get advice, which one would be better for me (have knowledge in Linux
I've been recently hit by
EnforcePartLimits=ALL
that refused jobs that couldn't run in all given partitions. Solved by
setting it to
EnforcePartLimits=ANY
so that the job gets queued if it can run in ANY given partition (very
useful if you also use JobSubmitPlugin=all_partitions ).
Diego
