Hi Jonathon,
I figured out, the problem is not the root owner ship but the way
/etc/init.d/slurm implements the "service slurm status", it checks the pid
file and caused permission issue. Why did it simply run "status slurmd"
which works perfectly?
I've modified the status and works fine now, thanks for your response.
status)
prog="${0##*/}d"
status ${prog}
;;
On Thu, Feb 11, 2016 at 1:05 PM, Jonathon A Anderson <
jonathon.ander...@colorado.edu> wrote:
> slurmd must run as root because it forks and execs processes on behalf of
> other users using the job owner’s uid.
>
> I don’t understand what trouble you’re having monitoring slurm with
> nagios. Could you give an example of what you’re trying to do, what you
> expect it to do, and what it does in stead?
>
> ~jonathon
>
>
> > On Feb 10, 2016, at 6:30 PM, jupiter <jupiter....@gmail.com> wrote:
> >
> > Hi,
> >
> > I am running slurm on CentOS 6. One thing I've just noticed is that the
> slurmctld is running under the user slurm but the slurmd is running under
> the root. Not quite sure why those daemons in different owner ships, any
> inside explanation please? Further looked at both slurm daemon configure in
> /etc/init.d and slurm.conf, they are identiccal, how could they behave
> differently? Anyway, can the owner ship of slurmd be changed to the user
> slurm?
> >
> > The problem I've got now is I am running nagios monitoring via ssh, it
> can check all other application daemon status, but it always failed to
> check slrum daemon status due to the slurmd root access restriction.
> >
> > Thanks.
> >
> >
>
>
