After last night's announcement, I decided to start the upgrade process.
Build went fine - once I worked out where munge went - and installation
also seemed fine.
slurmctld won't restart though.
In the logs I'm seeing:
[2018-05-31T15:20:50.810] debug: Munge encode failed: Failed to access
"xxx
On 31 May 2018 at 10:23, Lachlan Musicman wrote:
> Hola
>
> According to the documentation, the slurm munge rpm will be built if the
> munge libraries are installed.
>
> In CentOS 7.4 I have munge, munge-devel and munge-libs install, via yum.
> The libs are in /usr/lib64, the bins are in /usr/bin
Hola
According to the documentation, the slurm munge rpm will be built if the
munge libraries are installed.
In CentOS 7.4 I have munge, munge-devel and munge-libs install, via yum.
The libs are in /usr/lib64, the bins are in /usr/bin, the daemon is in
/usr/sbin.
Neither machine on which I run `
Slurm versions 17.02.11 and 17.11.7 are now available, and include a
series of recent bug fixes, as well as a fix for a security
vulnerability (CVE-2018-10995) related to mishandling of user names and
group ids.
Downloads are available at https://www.schedmd.com/downloads.php .
While fixes ar
Hello i have question, how run in background bash script in spank plugin ?
in my spank plugin in function : slurm_spank_task_init_privileged
i want to run this script :
system("nohup bash -c 'sleep 10 ; touch /tmp/newfile.txt' &");
i want to run in independant process this bash script, i don't
We are facing the same issues stated as SLURM Bug 4717 [1]. Moe Jette
clarified that in the old gres.conf manpage the statements about
Cores= parameter that "only the identified cores can be allocated with
each generic resource" is wrong, and the core binding setting is only
advisory by default.
W
