Your systemctl output shows that slurmctld is running OK, but that doesn't
match with your first entry, so it's hard to tell what's going on.
But if slurmctld won't start under systemd but it's not clear why the first
step would be to enable something like `SlurmctldDebug = debug` and check the
Thank you for your response.
I have found found out why there was no error in the log: I've been
looking at the wrong log. The error didn't occur on the master, but on
our vpn-gateway (it is a hybrid cloud setup) - but you can thin of it as
just another worker in the same network. The error I get
