Telegraf unable be write in InfluxDB cluster

,
1

Error:

2018-12-21T05:49:03Z E! [outputs.influxdb] when writing to [http://internal-influxdbdatalb-OpsTest-1031914036.us-west-2.elb.amazonaws.com:8088]: 200 OK 2018-12-21T05:49:03Z D! [outputs.influxdb] buffer fullness: 73961 / 1000000 metrics. 2018-12-21T05:49:03Z E! [agent] Error writing to output [influxdb]: could not write any address

InfluxDB Cluster:
Data Nodes ========== ID TCP Address Version 6 ip-10-8-1-200.us-west-2.compute.internal:8088 1.6.4-c1.6.4 5 ip-10-8-11-17.us-west-2.compute.internal:8088 1.6.4-c1.6.4 4 ip-10-8-2-74.us-west-2.compute.internal:8088 1.6.4-c1.6.4 7 ip-10-8-6-106.us-west-2.compute.internal:8088 1.6.4-c1.6.4 Meta Nodes ========== TCP Address Version ip-10-8-2-189.us-west-2.compute.internal:8091 1.6.4-c1.6.4 ip-10-8-7-16.us-west-2.compute.internal:8091 1.6.4-c1.6.4 ip-10-8-8-148.us-west-2.compute.internal:8091 1.6.4-c1.6.4

2

Not sure what the cause is, but based on the log messages Telegraf received a 200 response from the ELB but it is expecting a 204 response when it writes to InfluxDB.

3

Thank you .

I can see it started writing metrics in DB .

Still this error appears

Error writing to output [influxdb]: could not write any address

4

You are writing to the wrong port. The 8088 port is not used for what you expected.

Change the port to :8086 for http writes against InfluxDB from Telegraf. That should solve that problem.

5

I have tried the port 8086 . I’m getting error as this port is already being used .

Getting below error

2018-12-26T04:57:27Z E! [agent] Service for input inputs.http_listener failed to start: listen tcp :8086: bind: address already in use 2018-12-26T04:57:27Z E! [telegraf] Error running agent: listen tcp :8086: bind: address already in use

6

What server are you running?

It looks like you are running a telegraf_listener.

You need to update your influx output plugin to use port 8086. I would recommend you start from scratch on plugins and make it so your Telegraf instance can write to InfluxDB without the extra plugins like http_listener. Maybe just start with CPU. Then, add additional plugins until you figure out which one is breaking things