Hi,
I have a (hopefully quick) question: Do the slurm 19.05 cgroup plugins
know how to handle cgroup v2?
I'm setting up slurm on Fedora 32 and get the following error messages:
May 29 11:34:17 regulus slurmd[171632]: error: unable to mount cpuset
cgroup namespace: Device or resource busy
May 29
Good morning,
We have a cluster with two kind of infiniband cards, one connectx-4 and the
other connectx-6.
Openmpi-3.1.3 works fine, but when we start with connectx-6 we started to use
openmpi-4.0.3 (that support connectx-6) and the programs that have several
parts, first a call to a
Hi Ferran,
When you have a CentOS 7 system with the EPEL repo enabled, and you have
installed the munge RPM from EPEL, then things should be working correctly.
Since systemctl tells you that Munge service didn't start correctly,
then it seems to me that you have a problem in the general
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
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)
Thanks & Regards,
Sudeep
Hello everyone,
Here it comes everything I've done.
- About Ole's answer:
Yes, we have slurm as the user to control munge. Following your comment, I have
changed the ownership of the munge files and tried to start munge as munge
user. However, it also failed.
Also, I first installed munge
