Hey Gennaro,
Sure here it is:
ii slurm-client 15.08.7-1build1
amd64 SLURM client side commands
ii slurm-llnl 15.08.7-1build1
all transitional dummy package for slurm-wlm
ii slurm-llnl-slurmdbd 15.08.7-1build1
all transitional dummy package for slurmdbd
ii slurm-wlm 15.08.7-1build1
amd64 Simple Linux Utility for Resource Management
ii slurm-wlm-basic-plugins 15.08.7-1build1
amd64 SLURM basic plugins
ii slurmctld 15.08.7-1build1
amd64 SLURM central management daemon
ii slurmd 15.08.7-1build1
amd64 SLURM compute node daemon
ii slurmdbd 15.08.7-1build1
amd64 Secure enterprise-wide interface to a database for SLURM
________________________________________
From: slurm-users <slurm-users-boun...@lists.schedmd.com> on behalf of
slurm-users-requ...@lists.schedmd.com <slurm-users-requ...@lists.schedmd.com>
Sent: Saturday, September 29, 2018 2:00:01 PM
To: slurm-users@lists.schedmd.com
Subject: slurm-users Digest, Vol 11, Issue 46
Send slurm-users mailing list submissions to
slurm-users@lists.schedmd.com
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.schedmd.com/cgi-bin/mailman/listinfo/slurm-users
or, via email, send a message with subject or body 'help' to
slurm-users-requ...@lists.schedmd.com
You can reach the person managing the list at
slurm-users-ow...@lists.schedmd.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of slurm-users digest..."
Today's Topics:
1. Re: slurm-users Digest, Vol 11, Issue 45 (Alan Do-Omri)
2. Re: slurm-users Digest, Vol 11, Issue 45 (Gennaro Oliva)
----------------------------------------------------------------------
Message: 1
Date: Fri, 28 Sep 2018 21:42:23 +0000
From: Alan Do-Omri <alan.do-o...@mail.mcgill.ca>
To: "slurm-users@lists.schedmd.com" <slurm-users@lists.schedmd.com>
Subject: Re: [slurm-users] slurm-users Digest, Vol 11, Issue 45
Message-ID:
<ytxpr01mb0189ea2caf2f0f3c5946bfdee2...@ytxpr01mb0189.canprd01.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
I'm writing in response to the message below. I don't know how to reply in this
mailing list. Do we just reply to everyone?
And Eli, thank you for your help! Yes, the munge service is running. I am on
Ubuntu 16.04.10.
Message: 3
Date: Fri, 28 Sep 2018 13:24:30 -0400
From: Eli V <eliven...@gmail.com>
To: Slurm User Community List <slurm-users@lists.schedmd.com>
Cc: slurm-us...@schedmd.com
Subject: Re: [slurm-users] "cannot find auth plugin for auth/munge"
with slurm-llnl
Message-ID:
<cajtfhut-t_pzweapckchaklqc10wf5cbr5-tv0wdrhpf_yk...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Have you started the munge service? The order should be roughly, start
munge, start mysql/mariadb, start slurmdbd, start slurmctld, start
slurmd. You didn't mention which distribution you're using. On recent
debian versions the 3 slurm daemons have been split out independently
and you'll probably be better off installing them instead of the
slurm-llnl/wlm overall package since you only need the slurmdbd &
slurmctld on one or 2 nodes.
On Fri, Sep 28, 2018 at 12:52 PM Alan Do-Omri
<alan.do-o...@mail.mcgill.ca> wrote:
>
> Hey,
>
> I have been trying to set up slurm for the last few days but I keep stumbling
> upon the error whenever I run sudo slurmdbd -D:
> slurmdbd: error: Couldn't find the specified plugin name for auth/munge
> looking at all files
> slurmdbd: error: cannot find auth plugin for auth/munge
> slurmdbd: error: cannot create auth context for auth/munge
> slurmdbd: fatal: Unable to initialize auth/munge authentication plugin
>
> When I run sudo slurmd -D, I get the following errors:
> slurmd: slurmd version 15.08.7 started
> slurmd: error: Error binding slurm stream socket: Address already in use
> slurmd: error: Unable to bind listen port (*:6818): Address already in use
>
> I have set up my firewall to accept connections to these ports, however.
>
> When I run sudo sacctmgr -vvvv, I get the following:
> sacctmgr: debug3: Trying to load plugin
> /usr/lib/x86_64-linux-gnu/slurm/accounting_storage_slurmdbd.so
> sacctmgr: Accounting storage SLURMDBD plugin loaded with
> AuthInfo=/var/run/munge/munge.socket.2
> sacctmgr: debug3: Success.
> sacctmgr: debug2: slurm_connect failed: Connection refused
> sacctmgr: debug2: Error connecting slurm stream socket at 127.0.0.1:8080:
> Connection refused
> sacctmgr: debug: slurmdbd: slurm_open_msg_conn to localhost:8080: Connection
> refused
> sacctmgr: error: Problem talking to the database: Connection refused
>
> In my slurm.conf file I have
> SlurmUser=slurm
> SlurmctldPort=6817
> SlurmdPort=6818
> AuthType=auth/munge
> AccountingStorageType=accounting_storage/slurmdbd
> AccountingStoragePort=6819
> AccountingStorageHost=localhost
> #AccountingStorageLoc=
> AccountingStoragePass=/var/run/munge/munge.socket.2
> AccountingStorageUser=slurm
> (among other
>
> In my slurmdbd.conf file I have
> DbdAddr=localhost
> DbdHost=localhost
> DbdPort=6819
> SlurmUser=slurm
> StorageType=accounting_storage/mysql
> StoragePass=myslurmpassword
> StorageUser=slurm
> StorageLoc=slurm_acct_db
>
> and in the MySQL database, I have also done
> grant usage on *.* to 'slurm'@'localhost';
> grant all privileges on slurm_acct_db.* to 'slurm'@'localhost';
> flush privileges;
>
>
> Slurm was installed using sudo apt install slurm-llnl.
>
> I have done some research to try to solve this problem and I found some
> solutions but they didn't work for me. Two of them that I found were
> 1. To install munge development librairies: I have done this by doing sudo
> apt install libmunge-dev libmunge2
> 2. Using this
> https://groups.google.com/forum/#!searchin/slurm-users/unable$20to$20find$20auth$20munge%7Csort:date/slurm-users/Igm-moubmlM/OS26x2mNCAAJ
> to fix the library locations.
>
> Even after these two solutions, I am unable to fix the problem.
>
> Thank you for your help!
> Alan
------------------------------
Message: 4
Date: Fri, 28 Sep 2018 13:24:30 -0400
From: Eli V <eliven...@gmail.com>
To: Slurm User Community List <slurm-users@lists.schedmd.com>
Cc: slurm-us...@schedmd.com
Subject: Re: [slurm-users] "cannot find auth plugin for auth/munge"
with slurm-llnl
Message-ID:
<cajtfhut-t_pzweapckchaklqc10wf5cbr5-tv0wdrhpf_yk...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Have you started the munge service? The order should be roughly, start
munge, start mysql/mariadb, start slurmdbd, start slurmctld, start
slurmd. You didn't mention which distribution you're using. On recent
debian versions the 3 slurm daemons have been split out independently
and you'll probably be better off installing them instead of the
slurm-llnl/wlm overall package since you only need the slurmdbd &
slurmctld on one or 2 nodes.
On Fri, Sep 28, 2018 at 12:52 PM Alan Do-Omri
<alan.do-o...@mail.mcgill.ca> wrote:
>
> Hey,
>
> I have been trying to set up slurm for the last few days but I keep stumbling
> upon the error whenever I run sudo slurmdbd -D:
> slurmdbd: error: Couldn't find the specified plugin name for auth/munge
> looking at all files
> slurmdbd: error: cannot find auth plugin for auth/munge
> slurmdbd: error: cannot create auth context for auth/munge
> slurmdbd: fatal: Unable to initialize auth/munge authentication plugin
>
> When I run sudo slurmd -D, I get the following errors:
> slurmd: slurmd version 15.08.7 started
> slurmd: error: Error binding slurm stream socket: Address already in use
> slurmd: error: Unable to bind listen port (*:6818): Address already in use
>
> I have set up my firewall to accept connections to these ports, however.
>
> When I run sudo sacctmgr -vvvv, I get the following:
> sacctmgr: debug3: Trying to load plugin
> /usr/lib/x86_64-linux-gnu/slurm/accounting_storage_slurmdbd.so
> sacctmgr: Accounting storage SLURMDBD plugin loaded with
> AuthInfo=/var/run/munge/munge.socket.2
> sacctmgr: debug3: Success.
> sacctmgr: debug2: slurm_connect failed: Connection refused
> sacctmgr: debug2: Error connecting slurm stream socket at 127.0.0.1:8080:
> Connection refused
> sacctmgr: debug: slurmdbd: slurm_open_msg_conn to localhost:8080: Connection
> refused
> sacctmgr: error: Problem talking to the database: Connection refused
>
> In my slurm.conf file I have
> SlurmUser=slurm
> SlurmctldPort=6817
> SlurmdPort=6818
> AuthType=auth/munge
> AccountingStorageType=accounting_storage/slurmdbd
> AccountingStoragePort=6819
> AccountingStorageHost=localhost
> #AccountingStorageLoc=
> AccountingStoragePass=/var/run/munge/munge.socket.2
> AccountingStorageUser=slurm
> (among other
>
> In my slurmdbd.conf file I have
> DbdAddr=localhost
> DbdHost=localhost
> DbdPort=6819
> SlurmUser=slurm
> StorageType=accounting_storage/mysql
> StoragePass=myslurmpassword
> StorageUser=slurm
> StorageLoc=slurm_acct_db
>
> and in the MySQL database, I have also done
> grant usage on *.* to 'slurm'@'localhost';
> grant all privileges on slurm_acct_db.* to 'slurm'@'localhost';
> flush privileges;
>
>
> Slurm was installed using sudo apt install slurm-llnl.
>
> I have done some research to try to solve this problem and I found some
> solutions but they didn't work for me. Two of them that I found were
> 1. To install munge development librairies: I have done this by doing sudo
> apt install libmunge-dev libmunge2
> 2. Using this
> https://groups.google.com/forum/#!searchin/slurm-users/unable$20to$20find$20auth$20munge%7Csort:date/slurm-users/Igm-moubmlM/OS26x2mNCAAJ
> to fix the library locations.
>
> Even after these two solutions, I am unable to fix the problem.
>
> Thank you for your help!
> Alan
End of slurm-users Digest, Vol 11, Issue 45
*******************************************
------------------------------
Message: 2
Date: Sat, 29 Sep 2018 09:25:26 +0200
From: Gennaro Oliva <oliv...@na.icar.cnr.it>
To: Slurm User Community List <slurm-users@lists.schedmd.com>
Subject: Re: [slurm-users] slurm-users Digest, Vol 11, Issue 45
Message-ID: <20180929072526.GA2010@ischia>
Content-Type: text/plain; charset=us-ascii
Hi Alan,
On Fri, Sep 28, 2018 at 09:42:23PM +0000, Alan Do-Omri wrote:
> And Eli, thank you for your help! Yes, the munge service is running. I
> am on Ubuntu 16.04.10.
can you please send the output of the following command?
dpkg -l | grep slurm
Best regards
--
Gennaro Oliva
End of slurm-users Digest, Vol 11, Issue 46
*******************************************
