While moving a cluster from assigning node IP’s via DHCP to static assignment I had problems with the Nodes not properly setting the DNS server in /etc/resolve.conf when using /etc/hosts in Perceus to assign IP addresses. The nodes were defaulting to the values that were already in the vnfs capsule instead of updating them. This caused very slow ssh login times because the DNS server that was in the vnfs capsule /etc/resolve.conf file did not exist.
I wasn’t able to figure out how to fix this issue, so for now I just updated the resolve.conf file in the vnfs capsule.
For some background information on what led to this problem please see this old post: [intlink id=”87″ type=”post”]old post[/intlink].
Recently I’ve been working on moving a cluster from assigning node IP’s with DHCP to statically defined IP’s, in order to work around Torque/Moab not starting when it is unable to resolve the name of every node.
To do this, I entered all of the relevant information into the /etc/hosts file. But, after doing this and rebooting the nodes they were no longer automatically setting their hostname which had previously been retrieved from the DHCP server. Instead it would look like the following after logging in:
This can be solved by enabling the Perceus hostname module.
perceus module activate hostname
After enabling this it should like the following when logging into the nodes: