-
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 unable to start without existing log file #7905
Comments
this seems like a permission problem. Telegraf should have write permissions to the /var/log/telegraf folder. Make sure that the user running the telegraf process, or its group, has write access to this folder. |
@ssoroka i rolled back telegraf to 1.14.5 on the same host, no permissions changes or any other changes to the host besides yum downgrading. and the process started just fine. |
Did telegraf 1.15.1 add some new requirement to creating this log file? I'm working around things on my end, but would like to understand why a new telegraf version was responsble for breaking things. |
We are unable to start the In the 1.14.5 RPM
In the 1.15.1 it is owned by
It looks like the debian packages are working because there is a chown in the post install script: https://github.com/influxdata/telegraf/blob/master/scripts/deb/post-install.sh#L52 This is not present in the RPM post install script. |
Thanks for the follow up! Reopening |
should be resolved. Might have to wait for the nightly for the rpm to build to test. I reproduced locally in a VM and it seems to resolve the issue, so I'm thinking this should work. |
Relevant telegraf.conf:
System info:
Telegraf version 1.15.1, Amazon Linux 2018.03
Steps to reproduce:
/var/log/telegraf
directory exists, but has no filesExpected behavior:
Telegraf starts, and writes logs to
/var/log/telegraf/telegraf.log
Actual behavior:
Telegraf does not start
Additional info:
When rolling back our version to 14.5.1, telgraf starts correctly and logs to
/var/log/telegraf/telegraf.log
.Alternatively, if I manually create a blank log file named
/var/log/telegraf/telegraf.log
and chown it to telegraf, then version 1.15.1 will start correctly.This unexpectedly broke metrics reporting for us today on new hosts.
The text was updated successfully, but these errors were encountered: