failed to perform an HTTPS request: Post https://1.1.1.1/dns-query: EOF #2
Description
I am attempting to get cloudflared proxy-dns to work reliably but i have come across this error
time="2018-04-16T10:44:12Z" level=error msg="failed to connect to an HTTPS backend \"https://1.1.1.1/dns-query\"" error="failed to perform an HTTPS request: Post https://1.1.1.1/dns-query: EOF"
time="2018-04-16T10:44:13Z" level=error msg="failed to connect to an HTTPS backend \"https://1.1.1.1/dns-query\"" error="failed to perform an HTTPS request: Post https://1.1.1.1/dns-query: dial tcp 1.1.1.1:443: socket: too many open files"
Looking at netstat there is a large number of sockets stuck in the CLOSE_WAIT state.
tcp 386 0 124.188.xxx.xxx:56366 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56450 1.1.1.1:443 CLOSE_WAIT
tcp 385 0 124.188.xxx.xxx:56389 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56386 1.1.1.1:443 CLOSE_WAIT
tcp 387 0 124.188.xxx.xxx:56463 1.1.1.1:443 CLOSE_WAIT
tcp 387 0 124.188.xxx.xxx:56254 1.1.1.1:443 CLOSE_WAIT
tcp 385 0 124.188.xxx.xxx:56504 1.1.1.1:443 CLOSE_WAIT
tcp 385 0 124.188.xxx.xxx:56454 1.1.1.1:443 CLOSE_WAIT
tcp 387 0 124.188.xxx.xxx:56262 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56532 1.1.1.1:443 CLOSE_WAIT
tcp 387 0 124.188.xxx.xxx:56487 1.1.1.1:443 CLOSE_WAIT
tcp 387 0 124.188.xxx.xxx:56380 1.1.1.1:443 CLOSE_WAIT
tcp 385 0 124.188.xxx.xxx:56286 1.1.1.1:443 CLOSE_WAIT
tcp 387 0 124.188.xxx.xxx:56490 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56475 1.1.1.1:443 CLOSE_WAIT
tcp 387 0 124.188.xxx.xxx:56385 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56312 1.1.1.1:443 CLOSE_WAIT
tcp 387 0 124.188.xxx.xxx:56282 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56387 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56535 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56379 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56401 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56492 1.1.1.1:443 CLOSE_WAIT
tcp 385 0 124.188.xxx.xxx:56528 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56285 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56373 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56518 1.1.1.1:443 CLOSE_WAIT
tcp 385 0 124.188.xxx.xxx:56257 1.1.1.1:443 CLOSE_WAIT
tcp 387 0 124.188.xxx.xxx:56349 1.1.1.1:443 CLOSE_WAIT
tcp 385 0 124.188.xxx.xxx:56345 1.1.1.1:443 CLOSE_WAIT
tcp 387 0 124.188.xxx.xxx:56477 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56321 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56397 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56534 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56468 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56340 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56457 1.1.1.1:443 CLOSE_WAIT
tcp 386 0 124.188.xxx.xxx:56363 1.1.1.1:443 CLOSE_WAIT
I am running this on a ubiquity edge router Lite and after looking at the ulimit is set below.
root@ubnt:~# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 1934
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 1934
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited