SLURM uses the Munge library to get a signed credential for authentication. That uses a named pipe to communicate with the munge daemon on that node. If the named pipe does not exists, that probably means that the munge daemon is not running (look for "munged"). One unexpected thing though is the named pipe is "/var/run/munge/munge.socket.2" by default. I do not know why your path is listed as "/usr/local/var/run/munge/munge.socket.2" ________________________________________ From: [email protected] [[email protected]] On Behalf Of [email protected] [[email protected]] Sent: Thursday, May 12, 2011 7:17 AM To: [email protected] Subject: [slurm-dev] Problems with getting slurm/munge working
Hello guys, I'm a total newbie an this is my first try with slurm and munge. So i totally need your help.....please. i installed the newest slurm and munge. When i try to start some of the slurm daemons like for example sview or srun i always get an error based on munge. 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 srun: error: Munge encode failed: Unable to connect to "/usr/local/var/run/munge/munge.socket.2": Connection refused srun: error: authentication: Munged communication error Hope somebody can help me. regards, Marc P.S.: I'm running mung-0.5.10 and slurm-2.2.5 and the OS i'm using is openSuse 11.3 on a Virtual Machine (VBox-Host: Win7) P.P.S.: Sorry for my bad english!
