[slurm-users] [slurm-dev] Re: Installing SLURM locally on Ubuntu 16.04

Douglas Jacobsen dmjacobsen at lbl.gov
Wed Nov 8 07:01:29 MST 2017


Also please make sure you have the slurm-munge package installed (at least
for the RPMs this is the name of the package, I'm unsure if that packaging
layout was conserved for Debian)

----
Doug Jacobsen, Ph.D.
NERSC Computer Systems Engineer
National Energy Research Scientific Computing Center <http://www.nersc.gov>
dmjacobsen at lbl.gov

------------- __o
---------- _ '\<,_
----------(_)/  (_)__________________________


On Wed, Nov 8, 2017 at 5:46 AM, Manuel Rodríguez Pascual <
manuel.rodriguez.pascual at gmail.com> wrote:

> it looks like munge is not correctly configured, or you have some kind of
> permission problems. This manual explains how to configure and test it.
> https://github.com/dun/munge/wiki/Installation-Guide
>
> good luck!
>
> 2017-11-08 14:38 GMT+01:00 Will L <will.landau at gmail.com>:
>
>> Benjamin,
>>
>>
>> Thanks for following up. I just tried again as you said, with the
>> following result.
>>
>> $ sudo slurmctld -D -f /etc/slurm-llnl/slurm.conf
>> slurmctld: slurmctld version 17.02.9 started on cluster cluster
>> slurmctld: error: Couldn't find the specified plugin name for
>> crypto/munge looking at all files
>> slurmctld: error: cannot find crypto plugin for crypto/munge
>> slurmctld: error: cannot create crypto context for crypto/munge
>> slurmctld: fatal: slurm_cred_creator_ctx_create((null)): Operation not
>> permitted
>>
>> Will
>>
>> will-landau.com
>> linkedin.com/in/wlandau
>> github.com/wlandau
>>
>> On Sun, Nov 5, 2017 at 7:18 PM, Benjamin Redling <
>> benjamin.rampe at uni-jena.de> wrote:
>>
>>>
>>> Hi Will,
>>>
>>> looking at your stackoverflow postings there doesn't seem to be anything
>>> helpful. Did you solve your problem in the meantime?
>>>
>>> Am 30.10.2017 um 03:12 schrieb Will L:
>>> > I am trying to install SLURM 15.08.7 locally on an Ubuntu 16.04
>>> machine.
>>> > In my case, the master and worker nodes are the same.
>>> [...]
>>>
>>> Have you tried starting both slurmctld and slurmd in the foreground (-D)?
>>> When I have real trouble with a cluster I open two terminals
>>> side-by-side, set debugging in the slurm.conf to something reasonable
>>> high. Then I start...
>>> ... one with: slurmctld -D -f <path_to_config>
>>> ... another with: slurmd -D -f <path_to_config>
>>>
>>> (I only remember one case where that wasn't helpful: a seemingly random
>>> "user unknown" file access problem)
>>>
>>> Regards,
>>> Benjamin
>>> --
>>> FSU Jena | JULIELab.de/Staff/Benjamin+Redling.html
>>> ☎ +49 3641 9 44323
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20171108/0ff200df/attachment-0003.html>


More information about the slurm-users mailing list