I would try the following:
- adding worker node to /etc/host on controller machine (check if
controller has the correct IP),
- check slurm and munge logs,
- check if node and controller really have the same slurm.conf,
- /etc/init.d/slurm stop and then /etc/init.d/slurm startclean on node,
- try debug level to see if anything useful shows up in the logs.
Can you telnet/ping from controller to worker node?
Cheers,
Barbara
On 05/13/2014 09:00 AM, [email protected] wrote:
Hi Friends,
I have installed Slurm latest stable version on 2 node cluster.
The slurmcontroller is behaving as node as well, this node is
perfectly running fine,
But the other node with one cpu is show as down,
Followed everything noted here in this link:
https://computing.llnl.gov/linux/slurm/troubleshoot.html#nodes
Surprisingly, slurmd is getting the messages from the controller, but
controller is showing the reason as “Not Responding”.
[root@dhvanislclient ~]# scontrol show slurmd
Active Steps = NONE
Actual CPUs = 1
Actual Boards = 1
Actual sockets = 1
Actual cores = 1
Actual threads per core = 1
Actual real memory = 996 MB
Actual temp disk space = 8167 MB
Boot time = 2014-05-13T12:12:53
Hostname = dhvanislclient
Last slurmctld msg time = NONE
Slurmd PID = 22366
Slurmd Debug = 4
Slurmd Logfile = /var/log/slurm/slurmd.log
Version = 14.03.3
I am clueless right now, anyone for help?
Regards
Dhvani
The information contained in this electronic message and any
attachments to this message are intended for the exclusive use of the
addressee(s) and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of
viruses. The company accepts no liability for any damage caused by any
virus transmitted by this email.
www.wipro.com
