-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Output forward connections are in CLOSE_WAIT state #4618
Comments
Hi, Can anyone please help me out with the issue that I am facing ? |
Looks like we need more information to investigate this.
|
@daipom Thanks for responding. I see the below logs along with the logs that I have already shared.
I am not sure if these logs will help in analyzing better. Please let me know if you are looking for some specific keyword in the logs, I can try to get the output of those logs. |
Thanks! One more question.
Why does the server send reset packet? Could you attach server-side ( |
@daipom, I do not have access to the server-side logs. I was just checking the output plugin documentation, If we make the tcp connection as long-lived/persistent i.e., my setting Could this be the reason why fluentd is not able to clean-up connections in close_wait state.
|
No,
Here are the documents for plugin users. |
@daipom, ok sure, But I don't see CLOSE_WAIT connections getting closed. Am I missing any configuration that should be added? |
The However, the problem is that I can't reproduce this issue. I found out one thing. On non-Windows, However, when setting linger_timeout to <source>
@type forward
<transport tcp>
linger_timeout 1
</transport>
</source> However, in my testing, this was not a problem. |
At least, the close_wait socket should be closed after I need more information to reproduce the phenomenon... |
If you can, please try a more recent version. |
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 7 days |
Describe the bug
I have fluentd deployed as a deamonset in kubernetes cluster which is sending logs using output forward plugin. I have shared the config below. In the netstat output of fluentd, I see alot of close_wait connections. How can I resolve this ?
tcp 1 0 fluentd-operator-:<port> 1.1.1.1:<port> CLOSE_WAIT
To Reproduce
This issue is seen when the remote side of the connection has closed the connection.
Expected behavior
Ideally fluentd should handle closing the connection and relive the socket.
Your Environment
Your Configuration
Your Error Log
Additional context
No response
The text was updated successfully, but these errors were encountered: