You should double check the pam config too:

https://slurm.schedmd.com/faq.html#pam

Thanks,

Guy

On 16 February 2017 at 15:17, John Hearns <[email protected]> wrote:

> My answer is here maybe?
>
>
>
> https://slurm.schedmd.com/faq.html#memlock
>
>
>
> RTFM ?
>
>
>
> *From:* John Hearns [mailto:[email protected]]
> *Sent:* 16 February 2017 15:13
> *To:* slurm-dev <[email protected]>
> *Subject:* [slurm-dev] Slurm with sssd - limits help please
>
>
>
> Looks like there are others out there using slurm with sssd
> authentication, based on a quick mailing list search.
>
>
>
> Forgive me if I have not understood something here.
>
> On the cluster I am configuring at the moment, looking at the slurm daemon
> on the compute nodes
>
> it has the max locked memory limit set to unlimited.
>
> /etc/security/limits.conf has soft and hard max locked memory set to
> unlimited for all users.
>
>
>
> I tried to run an MPI job and got the familiar warning that there was not
> enough locked memory available..
>
> Looked at /etc/security/limits.conf as I have been bitten by that one
> before…
>
>
>
> I log in using an srun and sure enough:
>
>
>
> max locked memory       (kbytes, -l) 64
>
>
>
> It looks to me like the limits are being inherited from the /usr/sbin/sssd
> daemon
>
> In return this is started by systemd….
>
> (cue dark clouds, the howling of a wolf and the sound of thunder off-stage)
>
> At the moment I am looking at how to increase limits with systemd
>
>
>
> Please, someone tell me I’m an idiot and there is an easy way to do this.
>
> I weep though – is system really losing us the dependable and well known
> ways of doing things with limits.conf ??
>
> Any views or opinions presented in this email are solely those of the
> author and do not necessarily represent those of the company. Employees of
> XMA Ltd are expressly required not to make defamatory statements and not to
> infringe or authorise any infringement of copyright or any other legal
> right by email communications. Any such communication is contrary to
> company policy and outside the scope of the employment of the individual
> concerned. The company will not accept any liability in respect of such
> communication, and the employee responsible will be personally liable for
> any damages or other liability arising. XMA Limited is registered in
> England and Wales (registered no. 2051703). Registered Office: Wilford
> Industrial Estate, Ruddington Lane, Wilford, Nottingham, NG11 7EP
> Any views or opinions presented in this email are solely those of the
> author and do not necessarily represent those of the company. Employees of
> XMA Ltd are expressly required not to make defamatory statements and not to
> infringe or authorise any infringement of copyright or any other legal
> right by email communications. Any such communication is contrary to
> company policy and outside the scope of the employment of the individual
> concerned. The company will not accept any liability in respect of such
> communication, and the employee responsible will be personally liable for
> any damages or other liability arising. XMA Limited is registered in
> England and Wales (registered no. 2051703). Registered Office: Wilford
> Industrial Estate, Ruddington Lane, Wilford, Nottingham, NG11 7EP
>

Reply via email to