Failed to access "/usr/local/var/run/munge/munge.socket.2 No such file or directory (err=6) about munge HOT 7 CLOSED

@unitsmanolis,

I had the same issue in WSL2 running Ubuntu 22.04.

I fixed with:

sudo service munge start

Best,
Chris

from munge.

What is the path to the socket that the server is listening on? You can display the default path with munged -h | grep socket:

$ /usr/sbin/munged -h | grep socket
  -S, --socket=PATH        Specify local socket [/var/run/munge/munge.socket.2]

If munged is running, check to ensure that socket exists in the filesystem. This socket is created by munged when it is started, and removed by munged when it is gracefully shutdown (e.g., upon receiving a SIGTERM).

If this socket exists, check to ensure the client is using the same socket. Based on your output above, the client is using /usr/local/var/run/munge/munge.socket.2. The client has to connect to the same socket on which the server is listening. If the client & server are configured & built together, they will have the same default socket. You can force either the client or server to use an alternate socket with the -S or --socket command-line option. For example:

$ munge -n -S /var/run/munge/munge.socket.2

Original comment by chris.m.dunlap on 25 Nov 2014 at 10:12

• Added labels: Type-Support
• Removed labels: Type-Defect

from munge.

Original comment by chris.m.dunlap on 1 Dec 2014 at 10:54

• Changed state: Done

from munge.

I have the same problem. munged daemon create his socket in /run/munge while the client munge search /usr/local/var/run/munge. I have nastily fix it with a symbolic link.

Original comment by inf.maltese on 3 Apr 2015 at 4:26

from munge.

It sounds like you are running a client and daemon that were compiled separately with different configure options. As such, they have different default locations for the unix domain socket. This is discussed in #37.

Original comment by chris.m.dunlap on 3 Apr 2015 at 5:44

from munge.

Hi, I have a similar problem.

Window 10 with WSL

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal

$ which munge
/usr/bin/munge

$ sudo apt install munge

Reading package lists... Done
Building dependency tree
Reading state information... Done
munge is already the newest version (0.5.13-2build1).
0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.

$/etc/init.d/munge status
munged (pid 10078) is running

$sudo munge -n
munge: Error: Failed to access "/run/munge/munge.socket.2": No such file or directory

$/usr/sbin/munged -h | grep socket
-S, --socket=PATH Specify local socket [/run/munge/munge.socket.2]

$ cd /run/munge/
$ ls
#The folder is empty!

Many thanks

from munge.

@unitsmanolis Please open a new issue if you're having problems. This issue is closed.

from munge.