What steps will reproduce the problem?
1. Open many s2s connections
2. Be unlucky with garbage collection timeing
What is the expected output?
What do you see instead?
Large numbers of file descriptors for /etc/resolv.conf
Failed all the things
What version of the product are you using? On what operating system?
0.11.2 on Debian
Please provide any additional information below.
net.dns does not close the open file handle after parsing resolv.conf
In this case, someones with faulty DNS settings triggered a large number of s2s attempts which led to this problem.