We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes (a few times a day in our system) I encountered the failure to prepare a target with error messages like below.
2015-04-01 23:19:47 +0900 [error]: norikra/output.rb:131:rescue in prepare_target: failed to prepare target:stdout_ad norikra="norikra1.mtburn.internal:26571" error=Errno::ETIMEDOUT message="Connection timed out - connect(2) for \"norikra1.mtburn.internal\" port 26571 (http://norikra1.mtburn.internal:26571)" 2015-04-01 23:19:47 +0900 [error]: norikra/output.rb:99:block in register_worker: Failed to prepare norikra data for target:stdout_ad
I could simulated this situation that the thread to run register_worker stopped after the same failure.
This line has remained from v0.0.1, so I supposed this exception means something important.
But I want to avoid this failure (and subsequent forever RuntimeError until td-agent restart).
Is there any idea to avoid this failure ?
#6 is a similar issue about result except for type.
The text was updated successfully, but these errors were encountered:
Oh, this is bogus bug...
Sorry, something went wrong.
Thank you for reply. I pulled request #8.
a809183
I fixed this bug at a809183 and released v0.3.0. Targets should be retried. Thank you for reporting!
v0.3.0
Thanks !
No branches or pull requests
Sometimes (a few times a day in our system) I encountered the failure to prepare a target with error messages like below.
I could simulated this situation that the thread to run register_worker stopped after the same failure.
This line has remained from v0.0.1, so I supposed this exception means something important.
But I want to avoid this failure (and subsequent forever RuntimeError until td-agent restart).
Is there any idea to avoid this failure ?
#6 is a similar issue about result except for type.
The text was updated successfully, but these errors were encountered: