-
Notifications
You must be signed in to change notification settings - Fork 36
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
[manala.telegraf] service unable to start during initial provisioning #650
Comments
More investigation made and it seems the issue is only present with telegraf 1.25.0 (most recent one at the moment). The issue is caused by the fact, the official debian packages provided by influxdata automatically try to start the This looks like a bug of telegraf itself or/and telegraf official debian packages. I'm going to file an github issue on the official telegraf repository. For me, the workaround was simply to pick lower version of the telegraf to install from ansible playbook:
|
@nervo: thanks for the followup!
These are my ansible variables:
Roger that. FYI: I created an issue in telegraf github repo: influxdata/telegraf#12514 |
Ok, so let's wait for the next telegraf version :) (btw, you should also use explicit telegraf apt preference)
|
My bad. Thanks for pointing this out! |
manala.roles version: 3.2.0
During an initial provisioning of the node with
manala.telegraf
role attached, the service is not being started properly:As you can see, the configs are defined properly, but it seems they are not ready on service start.
The error I see in systemd:
During the 2nd provisioning attempt, the error is gone and the service starts normally.
The text was updated successfully, but these errors were encountered: