Skip to content
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 can't connect to influxdb #70

Open
zachjacobs opened this issue Jun 6, 2019 · 3 comments
Open

Telegraf can't connect to influxdb #70

zachjacobs opened this issue Jun 6, 2019 · 3 comments

Comments

@zachjacobs
Copy link

I've tried to run the default sandbox app on both Windows 10 and Ubuntu 18.04.2 with the same result. Is this a problem with the sandbox app or my usage?

I clone and type ./sandbox up

telegraf_1       | 2019-06-06T13:30:24Z I! Starting Telegraf 1.10.4
telegraf_1       | 2019-06-06T13:30:24Z I! Using config file: /etc/telegraf/telegraf.conf
telegraf_1       | 2019-06-06T13:30:24Z I! Loaded inputs: docker cpu system influxdb syslog mqtt_consumer
telegraf_1       | 2019-06-06T13:30:24Z I! Loaded aggregators: 
telegraf_1       | 2019-06-06T13:30:24Z I! Loaded processors: 
telegraf_1       | 2019-06-06T13:30:24Z I! Loaded outputs: influxdb
telegraf_1       | 2019-06-06T13:30:24Z I! Tags enabled: host=telegraf-getting-started
telegraf_1       | 2019-06-06T13:30:24Z I! [agent] Config: Interval:5s, Quiet:false, Hostname:"telegraf-getting-started", Flush Interval:5s
telegraf_1       | 2019-06-06T13:30:24Z W! [outputs.influxdb] when writing to [http://influxdb:8086]: database "telegraf" creation failed: Post http://influxdb:8086/query: dial tcp 172.19.0.2:8086: connect: connection refused
telegraf_1       | 2019-06-06T13:30:25Z E! [inputs.influxdb]: Error in plugin: [url=http://influxdb:8086/debug/vars]: Get http://influxdb:8086/debug/vars: dial tcp 172.19.0.2:8086: connect: connection refused
@openijl
Copy link

openijl commented Dec 1, 2019

Hi Zach, I have the same problem. Did you get a solution for this?

@dave4you
Copy link

@openijl, I have the same problem. Did you get a solution for this?

@maxwolffe
Copy link

maxwolffe commented Aug 24, 2020

FWIW - I had this issue on sandbox startup, but my data did end up successfully in influxdb.

Consider checking the influx logs for writes from telegraf:
./sandbox logs influxdb

You should see some regular writes from telegraf:

influxdb_1       | [httpd] 172.19.0.5 - - [24/Aug/2020:20:07:55 +0000] "POST /write?consistency=any&db=telegraf HTTP/1.1" 204 0 "-" "Telegraf/1.14.2" 7f405666-e645-11ea-811c-0242ac130002 38596
influxdb_1       | [httpd] 172.19.0.5 - - [24/Aug/2020:20:08:00 +0000] "POST /write?consistency=any&db=telegraf HTTP/1.1" 204 0 "-" "Telegraf/1.14.2" 823ad86e-e645-11ea-811d-0242ac130002 18210
influxdb_1       | [httpd] 172.19.0.5 - - [24/Aug/2020:20:08:05 +0000] "POST /write?consistency=any&db=telegraf HTTP/1.1" 204 0 "-" "Telegraf/1.14.2" 8535fbba-e645-11ea-811e-0242ac130002 29658

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants