-
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
Telegraf 1.21.0 - segmentation violation when using logparser #10286
Comments
The same here unter Debian Bullseye:
Reverting back to 1.20 works fine. |
@hluaces can you please also add this as a short note to the PR? |
Hi, even with Version 1.21.1 from last night it fails under Debian Bullseye:
|
@ohopp sorry for missing this one. Please check the artifacts on PR #10296 built by CI (once it finished). As a side note: |
Seeing something similar in the tail plugin I think
|
@jhass can you confirm you are running v1.21.1. We quickly rolled a patch release yesterday and it included a fix for |
Ah indeed, the package I'm using didn't update yet. Sorry for the noise! |
@hluaces can you please confirm that the mentioned PR fixes your issue!? |
Relevent telegraf.conf
System info
CentOS 7, Telegraf 1.21.0 (git: HEAD efa6522)
Docker
The Docker file is here:
https://github.com/hluaces/telegraf-bug-1.21.0
Please see the
README.md
for instructions on reproducing the error.Steps to reproduce
See the linked Dockerfile for instructions on how to reproduce.
Apparently the
tail
input seems to be failing when parsing logs. This did not happen in the1.20
branches.Expected behavior
Logs should be parsed without unexpected failures.
Actual behavior
Telegraf is failing with an error.
Additional info
This is the error output:
The text was updated successfully, but these errors were encountered: