What steps will reproduce the problem?
1. Open many s2s connections
2. Be unlucky with garbage collection timeing
3. ???
What is the expected output?
Nothing
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
Zash
on
Changes
owner Zash
tags Status-Started
Zash
on
In this case, someones with faulty DNS settings triggered a large number of s2s attempts which led to this problem.
What steps will reproduce the problem? 1. Open many s2s connections 2. Be unlucky with garbage collection timeing 3. ??? What is the expected output? Nothing 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.
Fixed in https://hg.prosody.im/trunk/rev/6402bc76f51a
ChangesThanks to Andi G. for unintentionally highlighting this problem.