I got other error message from fluentd.
failed to flush the buffer, retrying. error="no nodes are available"
The detail message is the following.
The reason
flunetd uses UDP for health check. But my target servers are on staging environment and collecting server is on production environment. They are on different segment. UDP is prohibited by our network policy.
The solution
Configure your Fire Wall to permit UDP over different segment.
Software Engineer is(should be) a most efficient Problem Solver.
Oct 12, 2012
fluentd unexpected error error="Address already in use - bind(2)"
When I started fluentd, I got the error message like the following.
2012-10-12 14:52:07 +0900: unexpected error error="Address already in use - bind(2)"
I searched which program was using this port. Yes, as you see it was td-agent(fluentd).
td-agent is supposed to use 24224 port. It's natural behavior.
But I forgot that I booted it by /usr/sbin/td-agent command before.
Yes it's absolutely my mistake. I killed this process and restart fluentd.
2012-10-12 14:52:07 +0900: unexpected error error="Address already in use - bind(2)"
I searched which program was using this port. Yes, as you see it was td-agent(fluentd).
td-agent is supposed to use 24224 port. It's natural behavior.
But I forgot that I booted it by /usr/sbin/td-agent command before.
Yes it's absolutely my mistake. I killed this process and restart fluentd.
Subscribe to:
Posts (Atom)