[tor-relays] unbound: error: recvfrom 123 failed: Host is down

[Winter Paulson]

Hey,

thanks for your answer teor.

I'm already running a full resolver. There is no firewall.

Regardless of the buffer size tuning I still see a lot of UDP drops due
to "no socket"


tor-exit# netstat -s -p udp
udp:
	48492539 datagrams received
	0 with incomplete header
	0 with bad data length field
	109 with bad checksum
	229788 with no checksum
	48262751 input packets software-checksummed
	29151016 output packets software-checksummed
	1466023 dropped due to no socket
	0 broadcast/multicast datagrams dropped due to no socket
	0 dropped due to missing IPsec protection
	0 dropped due to full socket buffers
	47026407 delivered
	92616440 datagrams output
	48490763 missed PCB cache


tor-exit# fstat | wc -l
   7716

/etc/sysctl.conf

kern.maxfiles=30000


/etc/login.conf

unbound:\
	:openfiles=13500:\
	:tc=daemon:

tor:\
    :openfiles-max=22000:\
    :tc=daemon:

Any ideas? thanks!

w.


On 11.12.19 02:24, teor wrote:
> Hi,
> 
>> On 8 Dec 2019, at 22:37, Winter Paulson <db8ltro2dy271kr3j9ucin3k at systemli.org> wrote:
>>
>> I'm running an exit relay > 200 Mbit/s with local unbound on openbsd. I
>> receive a lot of the following syslog messages from unbound:
>>
>> unbound: [15040:1] error: recvfrom 226 failed: Host is down
> 
> Maybe the remote DNS server can't handle the load?
> Or the network between you is dropping DNS packets?
> Or there's some firewall between you and the remote DNS that sees your DNS
> as problematic?
> 
> Have you tried running a full resolver?
> 
> T
> 
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>