Kiran, that's exactly what I've done, but I still get the same error messages.
Erica 2014-08-05 15:54 GMT-03:00 Kiran Thyagaraja <[email protected]>: > > You should be ideally specifying a directory under /var/spool > e.g /var/spool/slurm and then change its permissions so that the > SlurmUser can write to it. > > Kiran > > On 08/05/2014 01:33 PM, Mike Johnson wrote: > >> Re: [slurm-dev] >> >> Hi Erica >> >> What's the value of SlurmUser in the slurm.conf? >> >> You'll need to make sure the MailProg exists and is executable by the >> SlurmUser too >> >> Mike >> >> >> On 5 August 2014 18:20, Erica Riello <[email protected] <mailto: >> [email protected]>> wrote: >> >> Hi all, >> >> I've been trying to run the slurm controller daemon, but I get an >> error I have no idea how to solve: >> >> > sudo slurmctld -Dcvvvv >> slurmctld: pidfile not locked, assuming no running daemon >> slurmctld: error: Configured MailProg is invalid >> slurmctld: error: Job accounting information gathered, but not stored >> slurmctld: fatal: Incorrect permissions on state save loc: /var/spool >> >> >> Munge daemon is running and /var/spool permissions are: >> >> > ls -ld /var/spool >> drwxr-xr-x 10 root root 4096 Ago 5 13:31 /var/spool >> >> Does anyone knows how should /var/spool permissions be set? >> >> Thanks in advance. >> >> -- Erica >> >> >> -- =============== Erica Riello Aluna Engenharia de Computação PUC-Rio
