On Mon, Nov 13, 2017 at 10:15 AM, Benjamin Redling <
benjamin.ra...@uni-jena.de> wrote:
> On 11/12/17 4:52 PM, Gennaro Oliva wrote:
>
>> On Sun, Nov 12, 2017 at 10:03:18AM -0500, Will L wrote:
>>
>
> I just tried `sudo apt-get remove --purge munge`, etc., and munge itself
>>>
>>
> this should have
On 11/12/17 4:52 PM, Gennaro Oliva wrote:
On Sun, Nov 12, 2017 at 10:03:18AM -0500, Will L wrote:
I just tried `sudo apt-get remove --purge munge`, etc., and munge itself
this should have uninstalled slurm-wlm also, did you reinstalled it with apt?
seems to be working fine. But I still g
Hi Will,
On Sun, Nov 12, 2017 at 10:03:18AM -0500, Will L wrote:
> I just tried `sudo apt-get remove --purge munge`, etc., and munge itself
this should have uninstalled slurm-wlm also, did you reinstalled it with apt?
> seems to be working fine. But I still get `slurmctld: error: Couldn't find
>
Hi Will,
On Sun, Nov 12, 2017 at 11:07 PM, Will L wrote:
> In general, is Debian more cooperative with HPC systems than Ubuntu? Because
> I may just kill my KDE Neon installation and trying Debian + KDE Plasma.
By "HPC" systems, do you mean a server? Or a supercomputer??
As far as I know, no
In general, is Debian more cooperative with HPC systems than Ubuntu?
Because I may just kill my KDE Neon installation and trying Debian + KDE
Plasma.
will-landau.com
linkedin.com/in/wlandau
github.com/wlandau
On Sun, Nov 12, 2017 at 10:01 AM, Rajiv Nishtala
wrote:
>
>
> > On 12-Nov-2017, at 3:3
I just tried `sudo apt-get remove --purge munge`, etc., and munge itself
seems to be working fine. But I still get `slurmctld: error: Couldn't find
the specified plugin name for crypto/munge looking at all files`. Is there
a way to get around munge altogether? I am just testing on my local
machine,
> On 12-Nov-2017, at 3:33 PM, Raymond Wan wrote:
>
> Hi Rajiv,
>
> On Sun, Nov 12, 2017 at 9:47 PM, Rajiv Nishtala
> wrote:
>> it maybe that I’m missing context here - but in regards to munge, it makes
>> much more sense to follow the munge follow instructions from the GitHub of
>> munge.
Hi Rajiv,
On Sun, Nov 12, 2017 at 9:47 PM, Rajiv Nishtala wrote:
> it maybe that I’m missing context here - but in regards to munge, it makes
> much more sense to follow the munge follow instructions from the GitHub of
> munge.
> Remember, the permissions for the key and the /var/ and /etc fold
it maybe that I’m missing context here - but in regards to munge, it makes much
more sense to follow the munge follow instructions from the GitHub of munge.
Remember, the permissions for the key and the /var/ and /etc folder are
important
Best wishes,
Rajiv
> On 12-Nov-2017, at 2:14 PM, Gennar
Hi Will,
On Sat, Nov 11, 2017 at 07:12:59AM -0500, Will L wrote:
> I really think I mangled my system because I tried so many different
> things. Is there a way to start fresh without reinstalling my OS?
try purging and reinstalling munge, test it and than go on with slurm.
Remember to save you
I am trying what you said, but I am having new and earlier problems. For
example, now munge does not start.
$ sudo systemctl enable munge
Synchronizing state of munge.service with SysV init with
/lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable munge
Failed to
Hi Will,
On Thu, Nov 9, 2017 at 11:01 AM, Will L wrote:
>
> Thanks for the suggestions. Munge seems to be working just fine. At one point
> I tried to build SLURM from the source, but when I could not make it work, I
> `sudo make uninstall`ed it and opted for the pre-built apt version all over
Hi Will,
On Wed, Nov 08, 2017 at 10:01:31PM -0500, Will L wrote:
> SlurmUser=wlandau
you need change this to:
SlurmUser=slurm
Best regards
--
Gennaro Oliva
Thanks for the suggestions. Munge seems to be working just fine. At one
point I tried to build SLURM from the source, but when I could not make it
work, I `sudo make uninstall`ed it and opted for the pre-built apt version
all over again. Maybe that made a mess. What should I do to make SLURM
notice
Hi,
Sorry, to clarify, when the RPM spec file is used, it separates out the
slurm/crypto_munge.so slurm plugin into the slurm-munge RPM. I wasn't sure
if a debian package preparation did similar. To me, the log output
indicates that slurm/crypto_munge.so does not exist. If you are using a
./con
On 11/8/17 3:01 PM, Douglas Jacobsen wrote:
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)
nope, it's just "munge"
Regards,
Benjamin
--
FSU Jena | JULIELab.de
Hi Will,
On Wed, Nov 08, 2017 at 01:38:18PM +, Will L wrote:
> $ 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: er
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
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 :
> Benjamin,
>
>
> Thanks for following up. I just
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 al
20 matches
Mail list logo