[slurm-users] Unexpected missing socket error

[Ozeryan, Vladimir via slurm-users]

Hello everyone,

 

Not sure if you guys have heard this tune already but did anyone come across a solution for “Unexpected missing socket error”.
There is nothing useful in the logs but the message appears on compute nodes and slurm controller node.

 

Thank you,

 

Vlad Ozeryan

AMDS – AB1 Linux-Support

Vladimir...@jhuapl.edu

Ext. 23966

 

[Tilman Hoffbauer via slurm-users]

Hello,

we had this issue previously - it was connected to timeouts, where the socket disappeared due to a timeout before a reply could be sent back. In our case this was caused by having link-local multicast name resolution (LLMNR) on by default in systemd-resolved, which was evident by slow calls to `getent hosts <hostname>`.

Hope this helps,
Tilman Hoffbauer

[John Hearns via slurm-users]

As usual  - everything is a DNS (name resolution problem.

If your data centre is on fire, then your DNS server is burning. So it is a DNS problem.

--
slurm-users mailing list -- slurm...@lists.schedmd.com
To unsubscribe send an email to slurm-us...@lists.schedmd.com