Thank you so much for the reply, Andy. Well, apparently there's a lot happening that may be causing the issue. First, I can't seem to get slurmctld running properly. When I run "slurmctld -D", this is my output:
slurmctld: error: Can't save state, create file /var/spool/slurm/last_config_lite.new error Permission denied slurmctld: error: Configured MailProg is invalid slurmctld: Job accounting information stored, but details not gathered slurmctld: fatal: Incorrect permissions on state save loc: /var/spool/slurm I have the MailProg line in slurm.conf commented out, so does it have to be specified to work? Also, since I'm root and root is the owner of the /var/spool/slurm directory, I'm not sure why it's telling me the permissions are incorrect... On Thu, Mar 19, 2015 at 10:20 AM, Andy Riebs <andy.ri...@hp.com> wrote: > Michael, > > Try running "slurmctld -D" which should result in output telling you > what's going wrong. > > Andy > > > > On 03/19/2015 01:15 PM, Michael Kit Gilbert wrote: > > Sorry for the basic question, but I am new to slurm and am having some > basic problems with plugins. What I'd like to do is make the > job_submit_require_timelimit.so plugin that is found in the source code > active and required for all jobs. > > What I've done so far is I've added the line > > *PluginDir=/usr/lib64/slurm* > > to slurm.conf and I've created a plugstack.conf file that has one line > in it: > > *required job_submit_require_timelimit.so* > > And now slurm won't start at all. So obviously I've made a huge newbie > error. I've verified that our plugins are found in the /usr/lib64/slurm > directory, but I can't tell what else I need to do. > Does this plugin require arguments? Is there something else I'm missing? > > Thanks, > > Mike > > >
