View previous topic :: View next topic |
Author |
Message |
spica Guru
Joined: 04 Jun 2021 Posts: 329
|
Posted: Thu Sep 05, 2024 8:08 pm Post subject: dnsmasq: failed to send packet: Resource temporarily unavail |
|
|
Hi All,
For maybe a year I observe an issue with dnsmasq stops resolving names, in logs I see numerous "failed to send packet: Resource temporarily unavailable"
I can dig {somehostname} @8.8.8.8 – this works, bur dnsmasq doesn't.
Restart helps. But not for long time.
Does it make sense to try to fix it or maybe it makes sense (taking into account the recent news about bind-tools) to switch to isc bind?
Here is the part of a log where it was restarted manually: Code: | Sep 5 14:02:07 dnsmasq[2024]: failed to send packet: Resource temporarily unavailable
Sep 5 14:02:07 dnsmasq[2024]: failed to send packet: Resource temporarily unavailable
Sep 5 14:02:14 dnsmasq[2024]: failed to send packet: Resource temporarily unavailable
Sep 5 14:02:19 dnsmasq[2024]: failed to send packet: Resource temporarily unavailable
Sep 5 14:02:21 dnsmasq[2024]: exiting on receipt of SIGTERM
Sep 5 14:02:27 dnsmasq[6211]: started, version 2.90 cachesize 150
Sep 5 14:02:27 dnsmasq[6211]: compile time options: IPv6 GNU-getopt no-DBus no-UBus i18n no-IDN no-DHCP no-scripts no-TFTP no-conntrack ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Sep 5 14:02:27 dnsmasq[6211]: using nameserver 8.8.8.8#53
Sep 5 14:02:27 dnsmasq[6211]: using nameserver 8.8.4.4#53
Sep 5 14:02:27 dnsmasq[6211]: using nameserver 1.1.1.1#53
Sep 5 14:02:27 dnsmasq[6211]: using nameserver 1.0.0.1#53
Sep 5 14:02:27 dnsmasq[6211]: using nameserver 9.9.9.9#53
Sep 5 14:02:27 dnsmasq[6211]: using nameserver 149.112.112.112#53
Sep 5 14:02:27 dnsmasq[6211]: using only locally-known addresses for zzztest.oisd.nl
Sep 5 14:02:27 dnsmasq[6211]: using only locally-known addresses for zzux.com
Sep 5 14:02:27 dnsmasq[6211]: using only locally-known addresses for zzrjdp.xyz
Sep 5 14:02:27 dnsmasq[6211]: using only locally-known addresses for zzhyebbt.com
Sep 5 14:02:27 dnsmasq[6211]: using only locally-known addresses for zzhengre.com
Sep 5 14:02:27 dnsmasq[6211]: using only locally-known addresses for zzfoms.com
Sep 5 14:02:27 dnsmasq[6211]: using only locally-known addresses for zzbmxl.xyz
Sep 5 14:02:27 dnsmasq[6211]: using only locally-known addresses for zzaqqwecd.lat
Sep 5 14:02:27 dnsmasq[6211]: using 1133605 more local addresses
Sep 5 14:02:29 dnsmasq[6211]: read /etc/hosts - 2 names
Sep 5 17:43:12 dnsmasq[6211]: failed to send packet: Resource temporarily unavailable
Sep 5 17:43:12 dnsmasq[6211]: failed to send packet: Resource temporarily unavailable
Sep 5 17:43:12 dnsmasq[6211]: failed to send packet: Resource temporarily unavailable
Sep 5 17:43:12 dnsmasq[6211]: failed to send packet: Resource temporarily unavailable
Sep 5 17:43:12 dnsmasq[6211]: failed to send packet: Resource temporarily unavailable
Sep 5 17:43:12 dnsmasq[6211]: failed to send packet: Resource temporarily unavailable
Sep 5 17:43:12 dnsmasq[6211]: failed to send packet: Resource temporarily unavailable |
|
|
Back to top |
|
|
spica Guru
Joined: 04 Jun 2021 Posts: 329
|
Posted: Wed Sep 11, 2024 8:34 am Post subject: |
|
|
Send Queue is constantly growing, it looks like it grows each time I run dns lookup
Code: | # netstat -tulpan | egrep 'Send-Q|dnsmasq'
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 2076/dnsmasq
tcp 0 0 192.168.55.1:53 0.0.0.0:* LISTEN 2076/dnsmasq
tcp6 0 0 ::1:53 :::* LISTEN 2076/dnsmasq
tcp6 0 0 fe80::e0f7:5ff:fe7c::53 :::* LISTEN 2076/dnsmasq
udp 0 0 127.0.0.1:53 0.0.0.0:* 2076/dnsmasq
udp 0 83648 192.168.55.1:53 0.0.0.0:* 2076/dnsmasq
udp6 0 0 ::1:53 :::* 2076/dnsmasq
udp6 0 0 fe80::e0f7:5ff:fe7c::53 :::* 2076/dnsmasq |
At the number of 213376 it stopped serving responses. |
|
Back to top |
|
|
spica Guru
Joined: 04 Jun 2021 Posts: 329
|
Posted: Tue Sep 17, 2024 10:33 am Post subject: |
|
|
strace shows EAGAIN:
Code: | sendmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(62636), sin_addr=inet_addr("192.168.55.101")}, msg_namelen=16, msg_iov=[{iov_base="\16\331\201\200\0\1\0\t\0\0\0\0\nweatherapi\4intl\6xia"..., iov_len=208}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) |
In https://dnsmasq-discuss.thekelleys.org.narkive.com/Lke6UaTL/dnsmasq-on-high-load I found the next message, which sounds to me as a design flaw:
Quote: | there's one packet buffer and dnsmasq has to
either answer a request or forward it upstream before it can handle
the next - this code tries to be small in resource use. |
|
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|