-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
slurmdbd on separate host #2
Comments
Indeed, our current setup makes |
OK, thank you for the confirmation. |
Falkor
pushed a commit
that referenced
this issue
Feb 1, 2019
- Bugfix #2 Signed-off-by: Sebastien Varrette <Sebastien.Varrette@uni.lu>
Falkor
pushed a commit
that referenced
this issue
Feb 3, 2019
TRES, scheduler parameters and custom content management - Bugfix #2: slurmdbd on separate host bug - Bugfix #7: slurm-login nodes without daemons - Bugfix #12: slurm-17.11.3 install fails bug - Bugfix #13: Add SchedulerParameters to slurm.conf.erb template - Bugfix #14: Prevent improper use of SchedMD resources - Bugfix #16: Allow for TRESBillingWeights enhancement - Bugfix #17: Consolidate vagrant setup for module validation on a virtual cluster enhancement - Bugfix #18: Allow for custom content enhancement
uvNikita
pushed a commit
to uvNikita/puppet-slurm
that referenced
this issue
Apr 5, 2019
- Bugfix ULHPC#2 Signed-off-by: Sebastien Varrette <Sebastien.Varrette@uni.lu>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems like in the current implementation of the module
slurmdbd
andslurmctld
have to be on the same host. In particular,AccountingStorageHost
is set to the current control host in theslurm.conf
.puppet-slurm/templates/slurm.conf.erb
Line 206 in c5782ed
It seems that just using db host instead should fix the problem (note that I didn't actually test that):
I don't know much about slurm yet, so correct me please if I'm missing something.
The text was updated successfully, but these errors were encountered: