-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[1.2.1] slice bounds out of range #2488
Comments
It seems that this must be coming from the I think it's likely that this is fixed in 1.3, because the function that is panicking doesn't exist anymore, so it shouldn't panic but should instead raise an error when the metric gets written to InfluxDB (and will subsequently just be dropped). Would be good to figure out what the problem metrics are, so we can then write a unit-test that will catch it. |
My telegraf also crashes repeatedly using the following config:
log output:
|
@miniskipper I think your issue is unrelated, can you open it as a new issue and also include some sample logs and, ideally, try to find a sample log that reproduces the crash. |
Similar issue here when loading in an apache access_log w/ logparser:-
|
Closing, fixed in 1.3 |
Is there a workaround until 1.3 comes out? The influx service keeps crashing with the same runtime error. |
1.3 is out :) |
Bug report
Relevant telegraf.conf:
Steps to reproduce:
Seeing this panic fairly regularly:
Let me know what other information is needed!
The text was updated successfully, but these errors were encountered: