Do you have PAM enabled in SLURM? https://computing.llnl.gov/linux/slurm/faq.html#pam
On Mon, 24 Oct 2011 07:26:58 -0700, Matteo Guglielmi <[email protected]> wrote: > On all nodes we have: > > $ cat /etc/security/limits.conf > * soft memlock unlimited > * hard memlock unlimited > > > ############# jobfile ############### > #!/bin/bash > #SBATCH -o job-%N-%j.out > #SBATCH -J testlimits > #SBATCH --nodes=1 > > whoami > > echo > > hostname > > echo > > ulimit -a > > echo > > ulimit -l unlimited > > echo > > ulimit -a > > ulimit -s unlimited > > echo > > ulimit -a > ############################# > > $ sbatch job.sh > > Submitted batch job 1723 > > $ cat job-lbs02-1723.out > > software > > lbs02 > > core file size (blocks, -c) 0 > data seg size (kbytes, -d) 131072 > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 204800 > max locked memory (kbytes, -l) 32 <<<<<==== > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 <<<<===== > cpu time (seconds, -t) unlimited > max user processes (-u) 71680 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited > > /var/run/slurm/slurmd/job01723/slurm_script: line 18: ulimit: max locked > memory: cannot modify limit: Operation not permitted > > core file size (blocks, -c) 0 > data seg size (kbytes, -d) 131072 > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 204800 > max locked memory (kbytes, -l) 32 <<<<<==== > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 <<<<<==== > cpu time (seconds, -t) unlimited > max user processes (-u) 71680 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited > > core file size (blocks, -c) 0 > data seg size (kbytes, -d) 131072 > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 204800 > max locked memory (kbytes, -l) 32 <<<<<==== > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) unlimited <<<<<==== > cpu time (seconds, -t) unlimited > max user processes (-u) 71680 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited > > > But if I login directly on node "lbs02" via ssh both > "ulimit -l unlimited" and "ulimit -s unlimited" commands > give me no problem at all. > > [software@lbs02:~]$ ulimit -l unlimited > > [software@lbs02:~]$ ulimit -s unlimited > > [software@lbs02:~]$ ulimit -a > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 204800 > max locked memory (kbytes, -l) unlimited <<<<<==== > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) unlimited <<<<<==== > cpu time (seconds, -t) unlimited > max user processes (-u) 204800 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited > > > Thanks, > > --matt >
