On 10/29/20 12:56 PM, Paul Raines wrote:
The debugging was useful. The problem turned out to be that I am running with SELINUX enabled due to corporate policy. The issue was SELINUX is blocking sshd access to /var/slurm/spool/d socket files:
The documentation https://slurm.schedmd.com/pam_slurm_adopt.html describes some limitations:
* SELinux may conflict with pam_slurm_adopt, so it might need to be disabled. See also the author's page http://tech.ryancox.net/2015/11/pamslurmadopt.html /Ole
