-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failed to send packet: Resource temporarily unavailable #5664
Comments
Another reason is mentioned in
The ephemeral port range is limited in size (49152 to 65535 = 16383) and I'm not sure of LXC comes into play here - does the container have its own IP address or does it somehow share its address (and hence ports) with the host? There have been a few indications on the web that this could also happen when the MTU is unusually low and the UDP packet cannot be sent without blocking. But nothing here is really credible and worth quoting, I'm just mentioning this for the sake of completeness - maybe it rings a bell concerning your particular container configuration. So it seems we need more information. When this happens - does the Pi-hole stop working altogether?
What isn't clear to me: Do you want to show with the tcpdump snippet that receiving from the client works, sending + receiving from upstream as well and only sending back to the client is broken? Is it always the same behavior? Is it always the same client triggering this? Does you tcpdump show any further arriving queries or is there absolute silence after the last line in your snippet above?
|
This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days. |
@kornaz - just pinging you here in case you did not realise your original comment was split to a new thread |
For the last week or so I've been getting tons of "failed to send packet: Resource temporarily unavailable" errors. DNS stops working completely. Sometimes it recovers after ~10 minutes, sometimes I have to restart pihole-FTL. I've even added this restart to cron every two hours.
tcpdump shows that pihole receives the request and even forwards it to the upstream DNS server. Bet when upstream replies, pihole doesn't send the answer to the client.
Here x.136 is the client, x.108 is pihole and x.1 is the upstream DNS server.
BTW, running in Ubuntu 22.04 LTS LXC container with memory limited to 1GB. All the latest OS and pihole updates are installed.
Originally posted by @kornaz in #5608 (comment)
The text was updated successfully, but these errors were encountered: