Check /var/log/slurmctld.log and /var/log/slurmd.log
You can restart slurmctld in the foreground writing to stdout in verbose mode.
slurmctld -D -vvv
-D Run slurmctld in the foreground with logging copied to stdout.
-v Verbose operation. Multiple -v's increase verbosity.
-i Ignore errors found while reading in state files on startup.
+ [SLURM Troubleshooting](https://slurm.schedmd.com/troubleshoot.html)
+ [SLURM FAQ](https://slurm.schedmd.com/faq.html)
If slurmd is started with the -D option then the core file will be
written to the current working directory. Otherwise if SlurmdLogFile
is a fully qualified path name (starting with a slash), the core file
will be written to the same directory as the log file. Otherwise the
core file will be written to the SlurmSpoolDir directory, or
"/var/tmp/" as a last resort. If none of the above directories can be
written, no core file will be produced.