On 2013-12-23, Adam Thompson <athom...@athompso.net> wrote: > On 13-12-22 06:44 AM, Stuart Henderson wrote: >>> I'm seeing lots of "nsd[11026]: error: sendto failed: No route to host" >> You may need to raise net.inet.udp.sendspace > > Done. Raised from ~9000ish (default) to 41600. Errors still occurring > periodically, no perceptible change in rate. > If that was the problem in the first place, wouldn't the error be > different (ENOBUFS instead of EHOSTUNREACH)? > > If it's of any interest, the error often occurs in bursts (n>=4 within > syslog's "last message repeated /n/ times" window). >
Hmm, good point. Is there any chance you receive (and try to reply to) packets with bogus source addresses (spoofed/non-reachable, or packets which should have been natted but weren't)? I would also keep an eye on output of 'route -n monitor' and look for instability there (e.g. RTM_MISS messages).
