munge won't start about munge HOT 4 CLOSED

Re: Logfile is insecure: invalid ownership of "/var/log/munge": The /var/log/munge directory must either be owned by root or the EUID of the munged process. You are likely running munged under a different UID than that used during the "make install" which created the /var/log/munge directory. The quick fix is to chown /var/log/munge so it matches the UID under which munged is running.

Re: Unable to access "/var/run/munge/munge.socket.2": No such file or directory, munged is not currently running, and as such, hasn't created the socket required for client communication. Once you fix the above directory ownership, munged should start.

You can also try running munged with the --force command-line option which will override some of the less egregious security warnings.

Original comment by chris.m.dunlap on 11 May 2011 at 8:23

• Changed state: Invalid

from munge.

thanks for the fast answer. /usr/sbin/munged --force works but when i try for
example the quick benchmark with remunge i get the following error.

2011-05-11 22:34:24 Spawning 1 thread for encoding
2011-05-11 22:34:24 Processing credentials for 1 second
2011-05-11 22:34:34 Credential #1 encoding took 10.002 seconds
2011-05-11 22:34:34 Credential #1 encoding failed: Unable to connect to  "/usr/local/var/run/munge/munge.socket.2": Connection refused (err=6)
2011-05-11 22:34:34 Generated 1 encoding error
2011-05-11 22:34:34 Processed 0 credentials in 10.003s (0 creds/sec)

A similar error i receive when i try to start sview fom slurm

sview: error: Munge encode failed: Unable to connect to "/usr/local/var/run/munge/munge.socket.2": Verbindungsaufbau abgelehnt
sview: error: authentication: Munged communication error
sview: error: Munge encode failed: Unable to connect to "/usr/local/var/run/munge/munge.socket.2": Verbindungsaufbau abgelehnt
sview: error: authentication: Munged communication error

hope this is also easy to solve.

Original comment by MarcNowak83 on 11 May 2011 at 8:40

from munge.

The remunge client was unable to connect to the munged socket. It's likely due to permission and/or ownership problems that --force allowed you to override. The munged socket resides in /var/run/munge which should be permissioned 0755. Refer to the Installation Guide for recommended permissions.

Re: sview: It's trying to use /usr/local/var/run/munge/munge.socket.2, and the munged socket is located at /var/run/munge/munge.socket.2. That could also be contributing to the "connection refused / verbindungsaufbau abgelehnt" error.

Original comment by chris.m.dunlap on 11 May 2011 at 9:11

from munge.

Changed labels to indicate these were support issues.

Original comment by chris.m.dunlap on 3 Feb 2012 at 11:48

• Changed state: Done
• Added labels: Type-Support

from munge.