Hi Ole, Slurm is not broken, you just have some small configuration issues :)
Also, if you look at what's going on, it is kind of easy to locate the problems. For example, task 1.1 fails because executing "id" on you local resource and the remote one does not return the same result. If you look at what is different on the result, context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 a quick look into google returns that it is due to an specific configuration of SELinux, that you probably have different on your master and compute node. Similarly, you can go through the list of failed tests, carefully read the error, and try to solve them one by one. Good luck! Manuel 2014-11-26 15:16 GMT+01:00 Ole Holm Nielsen <[email protected]>: > Hi, > > Can anyone help in getting SLURM 14.11 to work correctly on CentOS 7.0? > > I'm testing SLURM 14.11 on CentOS 7.0. The default SLURM RPM is built by: > rpmbuild -ta slurm-14.11.0.tar.bz2. As a bare minimum test cluster, I have > a master PC running slurmctld, and just 1 compute node PC running slurmd > (see note below regarding bug in slurm systemctl). > > To verify my SLURM installation I have run the test script > testsuite/expect/regression, and unfortunately I get 13 FAILURE messages in > total: > > # grep FAILURE regression-25-Nov-2014.log > FAILURE: Login and slurm user info mismatch > test1.1 FAILURE > FAILURE: Login and slurm user info mismatch > test1.8 FAILURE > FAILURE: srun is not generating output (2 != 20) > test1.69 FAILURE > FAILURE: scontrol failed to find matching job (5 != 6) > FAILURE: waiting for job 7927 to run > FAILURE: scontrol failed to find all job steps > FAILURE: scontrol failed to specific job step > test2.8 FAILURE > test7.17 FAILURE > FAILURE: sacct reporting failed (3 < 4) > test12.2 FAILURE > FAILURE: Login and sbatch user info mismatch > test17.4 FAILURE > test17.35 FAILURE > test24.1 FAILURE > test24.3 FAILURE > test24.4 FAILURE > test30.1 FAILURE > test33.1 FAILURE > > (the full test output is in the attached file). > > Since I'm new to SLURM, I have no clue whether each of these failures are > benign or critical. I'm assuming that SLURM on CentOS 7 is broken until > someone more knowledgeable can help in decoding the test output. > > Maybe some tests fail because my "cluster" has only 1 compute node, but > who can tell if this is the case? > > BTW, the compute node slurmd unfortunately can't be started in the normal > way, as reported in bug 1182: "systemctl start/stop does not work on RHEL > 7", see http://bugs.schedmd.com/show_bug.cgi?id=1182. One must modify > /etc/slurm/slurm.conf and start slurm manually by: cd /etc/init.d; ./slurm > start. This bug should be fixed! > > My SLURM configuration is extremely simple: > > # sed '/^#/d' /etc/slurm/slurm.conf > ControlMachine=bell > MpiDefault=none > ProctrackType=proctrack/pgid > ReturnToService=1 > SlurmctldPidFile=/var/run/slurmctld.pid > SlurmdPidFile=/var/run/slurmd.pid > SlurmdSpoolDir=/var/spool/slurmd > SlurmUser=slurm > StateSaveLocation=/var/spool/slurmctld > SwitchType=switch/none > TaskPlugin=task/none > FastSchedule=1 > SchedulerType=sched/backfill > SelectType=select/linear > AccountingStorageType=accounting_storage/filetxt > ClusterName=cluster > JobAcctGatherType=jobacct_gather/linux > NodeName=hertz State=UNKNOWN CoresPerSocket=2 RealMemory=3688 TmpDisk=23988 > PartitionName=testing Nodes=hertz Default=YES MaxTime=3000 State=UP > > Thanks for any help, > Ole > > -- > Ole Holm Nielsen > Department of Physics, Technical University of Denmark > -- Dr. Manuel Rodríguez-Pascual skype: manuel.rodriguez.pascual phone: (+34) 913466173 // (+34) 679925108 CIEMAT-Moncloa Edificio 22, desp. 1.25 Avenida Complutense, 40 28040- MADRID SPAIN
