Error sending reply with sendto #844

Closed
pavel-odintsov opened this Issue Jun 4, 2013 · 9 comments

Projects

None yet

2 participants

@pavel-odintsov

Hello,

We use powerdnd from offical powerdns.com repo.

pdns_server --version
Version: 3.2, compiled on Jan 17 2013, 09:33:38 with gcc version 4.4.5

We have alot of record like this:
May 31 13:43:44 ns4 pdns[25236]: Error sending reply with sendto (socket=4): Invalid argument
May 31 13:43:48 ns4 pdns[25236]: Error sending reply with sendto (socket=4): Invalid argument
May 31 13:43:48 ns4 pdns[25236]: Error sending reply with sendto (socket=4): Invalid argument
May 31 13:43:53 ns4 pdns[25236]: Error sending reply with sendto (socket=4): Invalid argument
May 31 13:44:00 ns4 pdns[25236]: Error sending reply with sendto (socket=4): Invalid argument
May 31 13:44:06 ns4 pdns[25236]: Error sending reply with sendto (socket=4): Invalid argument

How to fix it?

@ahupowerdns
Member

Hi Pavel,

Can you share your configuration with us please? Also anything that could be interesting to know about your setup. Like operating system, for example. And which version of OS.

Thanks.

@pavel-odintsov

Debian 6, up-to-date, PDNS bind backend. iptables did not used. Are u need anything additional details?

@ahupowerdns
Member

yes, your pdns.conf please. The problem is likely to be in the local-address or local-ipv6 or local-port fields. Do you get this error for each packet, or only sometimes? What is your distributor-threads setting? Please send entire pdns.conf if possible.

@pavel-odintsov

Please take a took here: http://paste.org.ru/?pzo3lg

This error occurs on 4 from 4 our heavy loadad dns servers time to time.

@ahupowerdns
Member

are you perhaps adding and removing interfaces while in production? you bind to 0.0.0.0 which means we use tricks to send out the answer from the actual IP address that received the question.

You could change local-address to an actual IP address and see if the issue goes away.

@pavel-odintsov

Hello,

We did not do adding/removing interfaces. All 4 servers has only one network interface.

@Habbie Habbie added a commit that referenced this issue Jun 10, 2013
@Habbie Habbie fix message, refs #844 fe0b4a2
@ahupowerdns
Member

as an update, we still have no idea how or why this happens. This report is on our list of things to look at before 3.3, but we have no inspiration so far!

@pavel-odintsov

Hello, again!

We got new errors on git version of PDNS after activating IPv6 support:

Sep 20 21:26:35 ns2 pdns[2991]: Error sending reply with sendmsg (socket=4): Invalid argument
Sep 20 21:26:40 ns2 pdns[2991]: Error sending reply with sendmsg (socket=4): Invalid argument
Sep 20 21:26:47 ns2 pdns[2991]: Error sending reply with sendmsg (socket=4): Invalid argument
Sep 20 21:26:53 ns2 pdns[2991]: Error sending reply with sendmsg (socket=4): Invalid argument
Sep 20 21:26:59 ns2 pdns[2991]: Error sending reply with sendmsg (socket=4): Invalid argument
Sep 20 21:27:40 ns2 pdns[2991]: Error sending reply with sendmsg (socket=4): Invalid argument
Sep 20 21:28:04 ns2 pdns[2991]: Error sending reply with sendmsg (socket=4): Invalid argument
Sep 20 21:28:28 ns2 pdns[2991]: Error sending reply with sendmsg (socket=4): Invalid argument
Sep 20 21:28:33 ns2 pdns[2991]: Error sending reply with sendmsg (socket=4): Invalid argument
Sep 20 21:28:39 ns2 pdns[2991]: Error sending reply with sendmsg (socket=4): Invalid argument

@ahupowerdns
Member

this turns out to most likely be related to questions coming in from port 0! We now log the port number with this error.

@ahupowerdns ahupowerdns added a commit that closed this issue Mar 22, 2014
@ahupowerdns ahupowerdns No longer attempt to answer questions coming in from port 0, reply wo…
…uld not reach them anyhow. Thanks to Niels Bakker and sid3windr for insight & debugging.

Closes #844.
81859ba
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment