On 29-05-2020 08:46, Sudeep Narayan Banerjee wrote:
also check:
a) whether NTP has been setup and communicating with master node
b) iptables may be flushed (iptables -L)
c) SeLinux to disabled, to check :
getenforce
vim /etc/sysconfig/selinux
(change SELINUX=enforcing to SELINUX=disabled and save the file and reboot)
There is no reason to disable SELinux for running the Munge service.
It's a pretty bad idea to lower the security just for the sake of
convenience!
/Ole
On Fri, May 29, 2020 at 12:08 PM Sudeep Narayan Banerjee
<snbaner...@iitgn.ac.in <mailto:snbaner...@iitgn.ac.in>> wrote:
I have not checked on the CentOS7.8
a) if /var/run/munge folder does not exist then please double check
whether munge has been installed or not
b) user root or sudo user to do
ps -ef | grep munge
kill -9 <PID> //where PID is the Process ID for munge (if the
process is running at all); else
which munged
/etc/init.d/munge start
please let me know the the output of:
|$ munge -n|
|$ munge -n | unmunge|
|$ sudo systemctl status --full munge
|
Thanks & Regards,
Sudeep Narayan Banerjee
System Analyst | Scientist B
Indian Institute of Technology Gandhinagar
Gujarat, INDIA
On Fri, May 29, 2020 at 11:55 AM Bjørn-Helge Mevik
<b.h.me...@usit.uio.no <mailto:b.h.me...@usit.uio.no>> wrote:
Ferran Planas Padros <ferran.pad...@su.se
<mailto:ferran.pad...@su.se>> writes:
> I run the command as slurm user, and the /var/log/munge
folder does belong to slurm.
For security reasons, I strongly advise that you run munged as a
separate user, which is unprivileged and not used for anything else.
--
Regards,
Bjørn-Helge Mevik, dr. scient,
Department for Research Computing, University of Oslo
