The telegraf daemon is not enabled and so fails to start on reboot
Bug #1659375 reported by
Tim Kuhlman
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Telegraf Charm |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
On 3 machines that were recently rebooted telegraf didn't start back up. On investigation I simply needed to run 'systemctl start telegraf' and 'systemctl enable telegraf' to prepare for next reboot.
This was an older version of the charm installed at the end of September 2016, I have not yet tested with a newer charm.
Related branches
~paulgear/charm-telegraf:master
Merged
into
~telegraf-charmers/charm-telegraf:master
at
revision 3e9ba6cacf618f6d36f33d5c0f7f8ae7218ec38b
- Stuart Bishop (community): Approve
-
Diff: 11 lines (+1/-0)1 file modifiedreactive/telegraf.py (+1/-0)
Revision history for this message
| Paul Gear (paulgear) wrote | #1 |
| Changed in prometheus-charm: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Changed in telegraf-charm: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| Paul Gear (paulgear) wrote | #2 |
Revision history for this message
| Paul Gear (paulgear) wrote | #3 |
Revision history for this message
| Tim Kuhlman (timkuhlman) wrote | #4 |
| no longer affects: | prometheus-charm |
| Changed in telegraf-charm: | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Paul Gear (paulgear) wrote | #5 |
| Changed in telegraf-charm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I recently deployed a new environment with telegraf, and can confirm this behaviour. The telegraf package deploys in a disabled state, and the charm does nothing to fix this.