-
Notifications
You must be signed in to change notification settings - Fork 374
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
Parsing stops when hitting UTF-8 replacement char #698
Comments
This is definitely a bug, thanks for finding it! The problem is probably with how the file reader handles UTF-8 runes, and probably it's getting stuck by not discarding this after failing to convert the rune. Can you find the INFO logs for mtail when this happens? https://google.github.io/mtail/Troubleshooting.html#deployment-problems has the location of the INFO log. |
I ran mtail with -logtostderr, -one_shot and -v=2 and the output is attached in log files. Non-working log file: mtail_debug_nonworking.log Working log file: mtail_debug_working.log From the logs, I can only see the working one having one more |
Any news regarding this issue? Just so we know if we should find another solution or wait? |
I can't reproduce this on the latest build:
I get the same results from both of the example files you posted at the start. |
Great info. I will pass that forward and reopen a ticket if it's not solved in the new version. Thanks! |
We are using mtail to parse some specific logs where sometimes there are replacement chars(�) in strings. It seems like when mtail hits a log line with this char, it stops parsing logs after this log line.
mtail version: mtail version 3.0.0-rc50
mtail program:
Sample logs - non-working:
Sample logs - working:
Running with
-one_shot, with replacement char, I get
count_lines{prog="test"} 2and without it,
count_lines{prog="test"} 3`Is this a known problem and how can I get more info on why is it failing?
cc: @smrekarm12
The text was updated successfully, but these errors were encountered: