[slurm-users] slurmd startup problem

Brian Andrus toomuchit at gmail.com
Mon Aug 16 15:06:22 UTC 2021

I suspect you may have set some "frontendname" or "frontendaddr" in your 
slurm.conf that triggered that.

A FrontEnd is a node that is used to execute batch scripts rather than 
compute nodes (Cray ALPS systems). If that is not you, you should not 
set it.

Brian Andrus

On 8/16/2021 5:47 AM, Heckes, Frank wrote:
> Setting –disable-frontend as option for configure in slurm.spec or on 
> the configure command line ‘solved’ the issue.
> Is this a known bug?
> *From:*slurm-users <slurm-users-bounces at lists.schedmd.com> *On Behalf 
> Of *Heckes, Frank
> *Sent:* Monday, 16 August 2021 08:24
> *To:* Slurm User Community List <slurm-users at lists.schedmd.com>
> *Subject:* [slurm-users] slurmd startup problem
> Hi all,
> I’m using slurm version 20.02.01. After an OS update on a subset of 
> nodes to sles15.2 the compiled daemon, using the corresponding build 
> environment for sles15.2, fails to start with message:
> # slurmd -D -vvvvv -f /etc/slurm/slurm.conf
> slurmd: fatal: PrologFlags=alloc not supported on FrontEnd configurations
> Although the PrologFlags is set to ‘contain’ for all nodes. 
> Unfortunately no further debug information is printed.
> (This happens in the same way upon starting the daemon in configless mode)
> Does someone has an idea how to debug/solve this issue? Many thanks in 
> advance.
> Cheers,
> -Frank Heckes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20210816/75371400/attachment.htm>

More information about the slurm-users mailing list