Thank Ole, I checked the /etc/nsswitch.conf and I have even setup a dnsmasq service, just in case.
[root@slurm-simulator /]# cat /etc/nsswitch.conf | grep hosts # Valid databases are: aliases, ethers, group, gshadow, hosts, hosts: files dns myhostname [root@slurm-simulator /]# ping slurm-simulator -c 1 PING slurm-simulator (172.17.0.4) 56(84) bytes of data. 64 bytes from slurm-simulator (172.17.0.4): icmp_seq=1 ttl=64 time=0.022 ms --- slurm-simulator ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.022/0.022/0.022/0.000 ms [root@slurm-simulator /]# cat /etc/resolv.conf | grep -v "^#" nameserver 172.17.0.4 nameserver 172.31.0.2 search eu-west-3.compute.internal [root@slurm-simulator /]# host slurm-simulator slurm-simulator has address 172.17.0.4 [root@slurm-simulator /]# host 172.17.0.4 4.0.17.172.in-addr.arpa domain name pointer slurm-simulator. Regards, Jordi On Mon, 11 Jul 2022 at 23:09, Ole Holm Nielsen <ole.h.niel...@fysik.dtu.dk> wrote: > On 7/11/22 12:54, Jordi Blasco wrote: > > I use the front-end node mode > > <https://slurm.schedmd.com/faq.html#multi_slurmd> to emulate a real > > cluster in order to validate the Slurm configuration in a Docker > container > > and develop custom plugins. With versions 21.08.8-2 and 22.05.2, slurmd > is > > complaining about not being able to find the frontend node. > > > > slurmd -D -vvv > > ... > > slurmd: error: _find_node_record: lookup failure for node > "slurm-simulator" > > slurmd: error: _find_node_record: lookup failure for node > > "slurm-simulator", alias "slurm-simulator" > > slurmd: error: slurmd initialization failed > > This could be a DNS lookup issue. Can you ping the node named > "slurm-simulator"? > > /Ole > >
