-
Notifications
You must be signed in to change notification settings - Fork 57
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
Fluentd fails to start if gelf tcp output cannot connect #28
Comments
Hi @ivan-mjch , I also see this issue. I was trying shutting down Graylog to see if the retry works, and kind of worked:
But then I tried restarting Fluentd for a different reason, and started to get the errors you posted. Seems that as long as Fluentd is not restarted, Graylog connection errors will not break it. |
Hello ! The same problem here, we tried to secure our log. I try to explain, we use graylog to handle our logs so we use the gelf plugin. We would like to send our logs to graylog in normal situation, and if graylog falls keep the logs in a buffer file during this downtime. Currently our configuration seems to works:
But we have the same issue reported here. We stop td-agent/fluentd service, we stop graylog and we try to start again the td-agent/fluentd plugin. When we do that, we have the same behavior (loop) :
Any update on this issue ? Many thanks, |
Hello, This project is dead ? Regards, |
I haven't had much time to work on this ... you may want to look at one of the forks for your immediate needs. I am planning to rename my "parent" repo into an organization so we can get more maintainers involved directly. |
Hi @emsearcy, did you have a chance to look at this issue? The fork fluent-plugin-gelf-hs has the same issue. |
Sadly that fork disabled issues tab.. and this project isn't actively maintained :( |
yeah, I wish I had more time! I'm also not using Graylog any more ... I still love Graylog and Fluentd—both awesome tools—but it's hard to put in the time on a project I'm not running and have no live environments to test with. |
When fluentd is configured with a tcp gelf output, that cannot connect,
fluentd errors out, failing to start.
Centos 7 td-agent init scripts keep restarting fluentd, but it is not the expected behavior, as it halts all fluentd log processing and possibly results in message loss even in unrelated pipelines.
It may be related to #7, as fluentd core seems to be interacting improperly with the gelf library output connection. The problem may be in a difference between what fluentd expects and how gelf library behaves, that the plugin doesn't account for, but I don't know much about them.
The text was updated successfully, but these errors were encountered: