-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
New ASYNC net.dns.resolver fails with getaddrinfo(err=12): Timeout while contacting DNS servers with Elasticsearch shipper #7105
Comments
OS Windows Server 2012 R2, 64bit. With |
Do you know if the 2.0.10 releases work correctly? |
I have the same problem and saw this on version 2.0.10, 2.0.11 and 2.1.0. I am using the Some info:
[2023/04/19 05:15:00] [ warn] [net] getaddrinfo(host='<REDACTED>.', err=12): Timeout while contacting DNS servers
[2023/04/19 05:15:00] [error] [output:loki:loki.0] no upstream connections available
[2023/04/19 05:15:00] [ warn] [net] getaddrinfo(host='<REDACTED>.', err=12): Timeout while contacting DNS servers
[2023/04/19 05:15:00] [error] [output:loki:loki.0] no upstream connections available
[2023/04/19 05:15:00] [error] [upstream] connection #-1 to tcp://unavailable:0 timed out after 10 seconds (connection timeout)
... The output looks like the following:
Will try |
Almost 24 hours later, the DNS error seems gone after setting |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
This issue was closed because it has been stalled for 5 days with no activity. |
Reproduced in v1.8.11 & 1.9.7 with Elasticsearch plugin &
net.dns.resolver ASYNC
:Changing
net.dns.resolver
toLEGACY
resolved the problem in both versions.net.dns.resolver
is documented only in v1.9:https://docs.fluentbit.io/manual/v/1.9-pre/administration/networking
Similar reports:
Timeout while contacting DNS servers
with latest v2.19.1 aws/aws-for-fluent-bit#233The text was updated successfully, but these errors were encountered: