Hi Chris, On Wed, Aug 29, 2018 at 07:04:27AM +1000, Chris Samuel wrote: > On Tuesday, 28 August 2018 11:43:54 PM AEST Umut Arus wrote: > > > It seems the main problem is; slurmctld: fatal: No front end nodes defined > > Frontend nodes are for IBM BlueGene and Cray systems where you cannot run > slurmd on the compute nodes themselves so a proxy system must be used instead > (at $JOB-1 we used this on our BG/Q system). I strongly suspect you are not > running on either of those!
The option --enable-front-end to configure is also needed to emulate really large cluster: https://slurm.schedmd.com/faq.html#multi_slurmd > If you built Slurm yourself you'll need to check you didn't use those > arguments by mistake or configure didn't enable them in error, and if this is > an Ubuntu package then it's probably an bug in how they packaged it! This option is enabled only in the slurmctld daemon that is contained in the slurm-wlm-emulator package that is not intended to be used for batch jobs. vagrant@ubuntu-bionic:~$ grep 'No front end nodes defined' /usr/sbin/slurmctld-wlm-emulator Binary file /usr/sbin/slurmctld-wlm-emulator matches vagrant@ubuntu-bionic:~$ grep 'No front end nodes defined' /usr/sbin/slurmctld-wlm vagrant@ubuntu-bionic:~$ It can be possible that Umut installed slurm-wlm-emulator package together with the regular package and the emulated daemon was picked by the alternatives system. Best regards, -- Gennaro Oliva
