Telegraf shouldn't automatically attempt to connect to influxdb after installation

Bug #1916305 reported by Sergio Durigan Junior
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telegraf (Ubuntu)
Fix Released
Medium
Sergio Durigan Junior

Bug Description

After installation, telegraf will currently always try to connect to influxdb in order to output its metrics, but that is not ideal because influxdb might not be available. This also leads to a lot of pollution in the logs:

Feb 19 23:07:51 telegraf-hirsute telegraf[2133]: 2021-02-19T23:07:51Z W! [outputs.influxdb] When writing to [http://localhost:8086]: database "telegraf" creation failed: Post "http://localhost:8086/query": dial tcp [::1]:8086: connect: connection refused
Feb 19 23:08:01 telegraf-hirsute telegraf[2133]: 2021-02-19T23:08:01Z E! [outputs.influxdb] When writing to [http://localhost:8086]: failed doing req: Post "http://localhost:8086/write?db=telegraf": dial tcp [::1]:8086: connect: connection refused
Feb 19 23:08:01 telegraf-hirsute telegraf[2133]: 2021-02-19T23:08:01Z E! [agent] Error writing to outputs.influxdb: could not write any address
Feb 19 23:08:11 telegraf-hirsute telegraf[2133]: 2021-02-19T23:08:11Z E! [outputs.influxdb] When writing to [http://localhost:8086]: failed doing req: Post "http://localhost:8086/write?db=telegraf": dial tcp [::1]:8086: connect: connection refused
Feb 19 23:08:11 telegraf-hirsute telegraf[2133]: 2021-02-19T23:08:11Z E! [agent] Error writing to outputs.influxdb: could not write any address

Related branches

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package telegraf - 1.17.2+ds1-0ubuntu3

---------------
telegraf (1.17.2+ds1-0ubuntu3) hirsute; urgency=medium

  * d/rules: Disable test for inputs/riemann_listener.
    The test is currently failing with Go 1.16. The issue has been
    reported upstream.

 -- Sergio Durigan Junior <email address hidden> Sat, 20 Feb 2021 01:10:20 -0500

Changed in telegraf (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.