you will need to chown
> munge:munge after you have created it.
>
>
>
> Cheers
>
> L.
>
>
>
> *From:* Husen R [mailto:hus...@gmail.com]
> *Sent:* Thursday, 7 April 2016 12:07 PM
> *To:* slurm-dev
> *Subject:* [slurm-dev] Re: Failed to access munge.socket.2
&g
labama
Box 870346
Tuscaloosa, AL 36587
Office 205-348-3758 | Fax 205-348-9393
deborah.croc...@ua.edu
From: Husen R [mailto:hus...@gmail.com]
Sent: Wednesday, April 06, 2016 9:05 PM
To: slurm-dev
Subject: [slurm-dev] Re: Failed to access munge.socket.2
Hello Lachlan,Chris
Thank you for your reply
Hello all,
Currently I have installed and configured slurm-15.08.10 and munge-05.12
successfully.
-- it seems "/usr/local" appeared in the path to munge.socket.2 (
/usr/local/var/run/munge/munge.socket.2) because at configure step I
included it as a "--prefix" value. So I decided to reinstall
: Thursday, 7 April 2016 12:07 PM
To: slurm-dev
Subject: [slurm-dev] Re: Failed to access munge.socket.2
Hello Lachlan,Chris
Thank you for your reply.
I don't know why "/usr/local" is appended to the path..
I tried to locate munge.socket.2 manually using locate command and the file is
Hello Lachlan,Chris
Thank you for your reply.
I don't know why "/usr/local" is appended to the path..
I tried to locate munge.socket.2 manually using locate command and the file
is not exist indeed.
The directory /usr/local/var/run/munge is empty.
There is no munge directory in /var/run. I
On 06/04/16 19:50, Husen R wrote:
> however, when I tried to run sbatch I get the following error message:
>
> Failed to access "/usr/local/var/run/munge/munge.socket.2": No such file
> or directory
Is that path really correct?
On our systems it's: /var/run/munge/munge.socket.2
Best of luck,
Husen,
I’ve never seen a socket file in /usr/local
I feel like it should be in vanilla /var/run?
Because I had to build it, I discovered that I had to add a file to (I use
Centos, ymmv) /usr/lib/tmpfiles.d/munge.conf that looks like this:
d /var/run/munge 0755 munge munge –
Which meant that
