-
Notifications
You must be signed in to change notification settings - Fork 1.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
[ipv4/ipv6] Periodical log spams when hitting IPV6 endpoints and IPV6 is not supported by the VM #4473
Comments
The |
It's now [Update @ [Update @ Per discussion offline with @edsiper and @leonardo-albertovich , we are proposing two changes:
|
When a connection times out, an error message is dispatched informing the user about the event. In some cases the user would prefer to silent those messages by making them available only as 'debug' messages instead of an 'error'. This patch adds a new option to the upstream configuration: net.connect_timeout_log_error (default: true) This boolean option is enabled by default to keep the usual behavior but the user can turn it off in the OUTPUT section of the plugin so when a connection timeout is faced, it will be send a 'debug' message. Signed-off-by: Eduardo Silva <eduardo@calyptia.com>
When a connection times out, an error message is dispatched informing the user about the event. In some cases the user would prefer to silent those messages by making them available only as 'debug' messages instead of an 'error'. This patch adds a new option to the upstream configuration: net.connect_timeout_log_error (default: true) This boolean option is enabled by default to keep the usual behavior but the user can turn it off in the OUTPUT section of the plugin so when a connection timeout is faced, it will be send a 'debug' message. Signed-off-by: Eduardo Silva <eduardo@calyptia.com>
Related PR: #4474 |
When a connection times out, an error message is dispatched informing the user about the event. In some cases the user would prefer to silent those messages by making them available only as 'debug' messages instead of an 'error'. This patch adds a new option to the upstream configuration: net.connect_timeout_log_error (default: true) This boolean option is enabled by default to keep the usual behavior but the user can turn it off in the OUTPUT section of the plugin so when a connection timeout is faced, it will be send a 'debug' message. Signed-off-by: Eduardo Silva <eduardo@calyptia.com>
When a connection times out, an error message is dispatched informing the user about the event. In some cases the user would prefer to silent those messages by making them available only as 'debug' messages instead of an 'error'. This patch adds a new option to the upstream configuration: net.connect_timeout_log_error (default: true) This boolean option is enabled by default to keep the usual behavior but the user can turn it off in the OUTPUT section of the plugin so when a connection timeout is faced, it will be send a 'debug' message. Signed-off-by: Eduardo Silva <eduardo@calyptia.com>
When a connection times out, an error message is dispatched informing the user about the event. In some cases the user would prefer to silent those messages by making them available only as 'debug' messages instead of an 'error'. This patch adds a new option to the upstream configuration: net.connect_timeout_log_error (default: true) This boolean option is enabled by default to keep the usual behavior but the user can turn it off in the OUTPUT section of the plugin so when a connection timeout is faced, it will be send a 'debug' message. Signed-off-by: Eduardo Silva <eduardo@calyptia.com>
Verified that the short-term workaround to mute those logs worked for us. Leaving this open for the medium term solution, aka a new feature to enforce IPV4 address usage (basically ignore any IPV6 one) |
When a connection times out, an error message is dispatched informing the user about the event. In some cases the user would prefer to silent those messages by making them available only as 'debug' messages instead of an 'error'. This patch adds a new option to the upstream configuration: net.connect_timeout_log_error (default: true) This boolean option is enabled by default to keep the usual behavior but the user can turn it off in the OUTPUT section of the plugin so when a connection timeout is faced, it will be send a 'debug' message. Signed-off-by: Eduardo Silva <eduardo@calyptia.com>
closing this as resolved with #4501 |
Bug Report
Describe the bug
logging.googleapis.com
returns both IPV4 and IPV6 addresses. IPV6 is not supported out of the box on GCE VMs though. When IPV6 address is selected, Fluent Bit running on such a VM emits anerror
like below:For GCE, this is only happening on Windows 2016 VMs. (More details in #4300 (comment)).
It happens in a batch when the agent first starts up to init connections, and also in a batch every hour or so (This interval can change depending on how Fluent Bit is configured) when Fluent Bit needs to refresh connections.
GOOD (versions / commits that do not have this issue)
1.8.4
cd5b0bf8b1acf35310f0a56140287ac4395043e6
(1-8-4-with-chunkio-fix)BAD (versions that has this issue)
1.8.11
Ultimately it will retry and succeed with an
IPV4
address.Full log
The text was updated successfully, but these errors were encountered: