Look at /var/log/slurm/slurmctld.log On Tue, Jul 31, 2018 at 1:23 PM, Mahmood Naderan <mahmood...@gmail.com> wrote:
> I don't know what happened. It seems that it had been crashed before > > [root@rocks7 ~]# systemctl status slurmctld -l > ● slurmctld.service - Slurm controller daemon > Loaded: loaded (/usr/lib/systemd/system/slurmctld.service; enabled; > vendor preset: disabled) > Active: failed (Result: exit-code) since Tue 2018-07-31 20:02:24 +0430; > 1h 50min ago > Process: 28578 ExecStart=/usr/sbin/slurmctld $SLURMCTLD_OPTIONS > (code=exited, status=0/SUCCESS) > Main PID: 28583 (code=exited, status=1/FAILURE) > > Jul 31 20:02:23 rocks7.jupiterclusterscu.com systemd[1]: Starting Slurm > controller daemon... > Jul 31 20:02:23 rocks7.jupiterclusterscu.com systemd[1]: PID file > /var/run/slurmctld.pid not readable (yet?) after start. > Jul 31 20:02:23 rocks7.jupiterclusterscu.com systemd[1]: Started Slurm > controller daemon. > Jul 31 20:02:24 rocks7.jupiterclusterscu.com systemd[1]: > slurmctld.service: main process exited, code=exited, status=1/FAILURE > Jul 31 20:02:24 rocks7.jupiterclusterscu.com systemd[1]: Unit > slurmctld.service entered failed state. > Jul 31 20:02:24 rocks7.jupiterclusterscu.com systemd[1]: > slurmctld.service failed. > > > Regards, > Mahmood > > > > On Tue, Jul 31, 2018 at 9:32 PM, Alex Chekholko <a...@calicolabs.com> > wrote: > >> Seems like your slurmctld is not running. Have you checked its log to >> see why? >> >>> >>> >>> Regards, >>> Mahmood >>> >>> >>> > -- Hadrian Djohari Manager of Research Computing Services, [U]Tech Case Western Reserve University (W): 216-368-0395 (M): 216-798-7490
