-
Notifications
You must be signed in to change notification settings - Fork 12
We're using the fluent-plugin-multiprocess plugin and sometimes td-agent binds to 0.0.0.0 instead of 127.0.0.1 #10
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
Comments
Hmm... where is the logs which td-agent tries to bind 0.0.0.0 instead of 127.0.0.1? |
Hi Masahiro, please find attached: You can grep for EADDRINUSE - it might be something around there. |
I did grep your log, but there are no log lines with
|
EADDRINUSE means other process has already used same port. |
Hi - The times we see it bind to 0.0.0.0 (which we don't want and don't have errors for) is when we get an EADDRINUSE for "127.0.0.1". ERROR EXAMPLE - td-agent didn't come up on both TCP and UDP on localhost. UDP came up on 0.0.0.0 only. We can see an EADDRINUSE in the logs for 127.0.0.1.
WORKING EXAMPLE - td-agent comes up on both localhost for both UDP and TCP
When we see td-agent bind to 0.0.0.0 we see the EADDRINUSE for 127.0.0.1. Binding to 0.0.0.0 is an error for us since we have it configured to bind to 127.0.0.1 in our configurations. |
Hi-
We're using the fluent-plugin-multiprocess plugin and sometimes td-agent binds to 0.0.0.0 instead of 127.0.0.1, when we have the following specified in our configs:
This prevents things from actually shipping logs for us on that specific port, in those times td-agent binds to 0.0.0.0 instead of localhost 127.0.0.1. The issue recurs often, but is not consistently reproducible for us and the logs just say:

The "fix"/remediation for the issue has been to just stop/start td-agent, which then allows td-agent to bind to localhost instead of 0.0.0.0.
The versions from the startup of the agent are:
If you have and advice on what the issue might be, it'd be much appreciated.
Best regards!!!!
Jonathan
The text was updated successfully, but these errors were encountered: