-
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
logparser should error and exit on permissions errors #1418
Comments
Similar issue on RedHat EL5! Also with tail plugin! |
It's probably a permissions issue, try running |
that being said, if it is a permissions issue, there should be an error message about that. |
I just made the test and you're right @sparrc this is about permission on log file. Thank you ! Add an error message to the log will help the user. :) |
I installed Telegraf this morning and configured logparser. Nothing's been written all day, and I suspect its permissions. Telegraf gives no indicator of that in /var/log/telegraf/telegraf.log, though |
closes #1436 This also fixes the bad behavior of waiting until runtime to return log parsing pattern compile errors when a pattern was simply unfound. closes #1418 Also protect against user error when the telegraf user does not have permission to open the provided file. We will now error and exit in this case, rather than silently waiting to get permission to open it.
I'm testing the awesome new logparser plugin but I have trouble to made it work.
Actually with this version
Running it on Ubuntu 14.04
This is my conf with logparser
This settings works when I type
telegraf
in my console but not work when I launch telegraf withservice telegraf start
When I launch telegraf in my console I can see the lines
But when I launch it from
service telegraf start
this is the lines in logfileThe line with
Seeked
is not presentsIf I set only the logparser plugin, there is 0 metric gathered.
Maybe this is normal due to the beta release ?
The text was updated successfully, but these errors were encountered: