No munge.socket.2 file about munge HOT 5 CLOSED

This socket is created by the daemon (munged). Check to make sure munged is running.

Before starting munged for the first time, you'll need to create a secret key:

# dd if=/dev/urandom of=/etc/munge/munge.key bs=1 count=1024
# chmod 400 /etc/munge/munge.key
# chown munge:munge /etc/munge/munge.key

This key will need to be securely copied to all hosts within the MUNGE realm.

Once this key is created, you'll need to start munged:

# /usr/sbin/munged --force

On Ubuntu 14.04, you'll need to run munged with the --force option for now due to #31.

By default, munged will perform a double-fork to run in the background. If the socket is not being created or the daemon is not running, you can check the logfile (/var/log/munge/munged.log) or run munged in the foreground to have errors dumped to the terminal (/usr/sbin/munged --force --foreground).

Original comment by chris.m.dunlap on 31 Jul 2014 at 9:08

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

from munge.

Original comment by chris.m.dunlap on 5 Aug 2014 at 12:10

• Changed state: Done

from munge.

Thank you, it worked just fine!

Original comment by ericaflriello on 5 Aug 2014 at 12:49

from munge.

Now I'm experiencing this problem again in a new installation, but this time I noted munge daemon creates munge.socket.2 in /usr/local/var/run/munge instead of creating it in /var/run/munge.

I've tried re-installing, but nothing changes that. Do you know what might be wrong this time?

Original comment by ericaflriello on 5 Sep 2014 at 1:56

from munge.

The socket is created in $(localstatedir)/run/munge. $(localstatedir) defaults to $(prefix)/var, and $(prefix) defaults to /usr/local; hence /usr/local/var/run/munge.

You probably want to configure it with something like:

$ ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var

Original comment by chris.m.dunlap on 5 Sep 2014 at 4:42

from munge.