Recently I enabled accounting on my tiny (1 compute node, one head node) slurm cluster.
slurmdbd.conf looks like
AuthType=auth/munge DbdHost=vertex DbdPort=6819 SlurmUser=slurm StorageHost=localhost StorageType=accounting_storage/mysql StorageUser=slurm StoragePass=#elided# StoragePort=3306 StorageLoc=slurm_acct_db PurgeEventAfter=30days PurgeJobAfter=30days PurgeResvAfter=30days PurgeStepAfter=30days PurgeSuspendAfter=30days
Some potentially relevant parts of slurmd.conf are:
UsePAM=1 ProctrackType=proctrack/cgroup SelectTypeParameters=CR_Core_Memory AccountingStorageType=accounting_storage/slurmdbd ClusterName=simplex JobCompType=jobcomp/none JobAcctGatherFrequency=30 JobAcctGatherType=jobacct_gather/cgroup
Since I enabled accounting the output from every job (whether started by srun or sbatch) finishes with
slurmstepd-simplex: error: pam_close_session: Cannot make/remove an entry for the specified session
/etc/pamd.d/slurm has the following content
auth required pam_localuser.so auth required pam_shells.so account required pam_unix.so account required pam_access.so session required pam_unix.so session optional pam_systemd.so
Accounting seems to be working OK.
Does anyone know what PAM related code paths could be triggered by enabling accounting?
d