From what I know of how this works, no, it’s not getting it from a local file
or the master node. I don’t believe it even makes a network connection, nor
requires a slurm.conf in order to run. If you can run it fresh on a node with
no config and that’s what it comes up with, it’s probably gettin
On 3/12/20 9:37 PM, Kirill 'kkm' Katsnelson wrote:
Aaah, that's a cool find! I never really looked inside my nodes for more
than a year since I debugged all my stuff so it "just works". They are
conjured out of nothing and dissolve back into nothing after 10 minutes
of inactivity. But good to
On Wed, Mar 11, 2020 at 9:57 PM Chris Samuel wrote:
> If so move it out of the way somewhere safe (just in case) and try again.
>
Aaah, that's a cool find! I never really looked inside my nodes for more
than a year since I debugged all my stuff so it "just works". They are
conjured out of nothin
Hello,
while upgrading slurm from 19.05 to 20.02 an error occurred while trying to
upgrade slurmdbd first.
The error is:
slurmdbd: debug: Munge authentication plugin loaded
slurmdbd: debug2: mysql_connect() called for db slurm_acct_db
slurmdbd: debug2: Attempting to connect to slurmmaster:3306
Hi all,
I compiled Slurm 18.08.7, 19.05.5 and 20.02.0 on Ubuntu 18.04 server.
X-Forwarding works fine with 18.08.7.
* (19.05.5 / 20.02.0) However, slurmd logs the following error message
for version 19.05.5 and 20.02.0 when start a GUI application, for example:
[2020-03-11T11:42:55.673] [
