On 27/10/22 4:18 am, Gizo Nanava wrote:
we run into another issue when using salloc interactively on a cluster where
Slurm
power saving is enabled. The problem seems to be caused by the job_container
plugin
and occurs when the job starts on a node which boots from a power down state.
If I resu
On 27/10/22 11:30 pm, Richard Chang wrote:
Yes, the system is a HPE Cray EX, and I am trying to use
switch/hpe_slingshot.
Which version of Slurm are you using Richard?
All the best,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA
On 30/10/22 12:27 pm, Davide DelVento wrote:
But if I understand correctly your Prolog vs TaskProlog distinction,
the latter would have the environmental variable and run as user,
whereas the former runs as root and doesn't get the environment,
That's correct. My personal view is that injectin
Hi,
I have two dedicated nodes for slurm, node1 and node2.
I have created the following.
*Role*
*SlurmCTLD*
*SlurmDBD*
*Mariadb Server for accounting storage*
*Primary*
Node1
Node2
Node2
*Backup*
Node2
Nod
Hi Chris,
> Unfortunately it looks like the license request information doesn't get
> propagated into any prologs from what I see from a scan of the
> documentation. :-(
Thanks. If I am reading you right, I did notice the same thing and in
fact that's why I wrote that job_submit lua script which
On 30/10/22 10:23 am, Chris Samuel wrote:
Unfortunately it looks like the license request information doesn't get
propagated into any prologs from what I see from a scan of the
documentation. 🙁
This _may_ be fixed in the next major Slurm release (February) if I'm
reading this right:
https:
On 29/10/22 7:37 am, Davide DelVento wrote:
So either I misinterpreted that "same environment as the user tasks"
or there is something else that I am doing wrong.
Slurm has a number of different prologs that can run which can cause
confusion, and I suspect that's what's happening here.
The
