munge.socket.2 not created

[isturzunano]

I am trying to run a small batch script after installation of slurm and munge and I getting this error:
`
sbatch: error: If munged is up, restart with --num-threads=10

sbatch: error: Munge encode failed: Failed to access "/run/munge/munge.socket.2": No such file or directory

sbatch: error: slurm_send_node_msg: auth_g_create: REQUEST_SUBMIT_BATCH_JOB has authentication error

sbatch: error: Batch job submission failed: Protocol authentication error
`
Can you please help? Thank you.

[dun]

It appears munged is not running. Create a key, copy it to all nodes in the cluster, and start munged on each host. I don't think you need to specify --num-threads=10. The default is to run with 2 threads which should generally be sufficient.

See:

• https://github.com/dun/munge/wiki/Installation-Guide#common-errors
• https://github.com/dun/munge/wiki/Installation-Guide#configuration-and-setup
• https://github.com/dun/munge/wiki/Installation-Guide#starting-and-stopping-the-daemon

[isturzunano]

Thank you for the quick reply. I think my problems are coming from an old attempt to install when I used root for everything. Is there a standard way to clean a munge installation?

…

On 4/8/22 20:00, Chris Dunlap wrote: It appears munged is not running. Create a key, copy it to all nodes in the cluster, and start munged on each host. I don't think you need to specify |--num-threads=10|. The default is to run with 2 threads which should generally be sufficient. See: * https://github.com/dun/munge/wiki/Installation-Guide#common-errors * https://github.com/dun/munge/wiki/Installation-Guide#configuration-and-setup * https://github.com/dun/munge/wiki/Installation-Guide#starting-and-stopping-the-daemon — Reply to this email directly, view it on GitHub <#118 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWT4ET7G2ZI532E4ZZFKCLTVEDJCLANCNFSM5S5VBMWQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[dun]

If you installed it using a package manager, there should be a corresponding package manager command to remove it.

If you installed it with make install, there is a corresponding make uninstall. If you installed as root, you will need to uninstall as root.