Influxdb Error Please solution


#1

Hi,
2018-06-04T04:04:36Z E! [outputs.influxdb]: when writing to [http://172.16.11.47:8086]: Post http://172.16.11.47:8086/write?db=telegraf: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

Please solution

Thanks


#2

Please add more detail to this post so that someone can help you.

What are the steps to reproduce this error? What troubleshooting steps have you already tried?

The most obvious cause of a timeout would be network connectivity issues, so that would be a good place to start investigating.


#3

this error in telegraf log, why?

2018-06-04T03:58:10Z E! [outputs.influxdb]: when writing to [http://172.16.11.47:8086]: Post http://172.16.11.47:8086/write?db=telegraf: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
2018-06-04T03:58:10Z E! Error writing to output [influxdb]: could not write any address
2018-06-04T03:58:15Z E! [outputs.influxdb]: when writing to [http://172.16.11.47:8086]: Post http://172.16.11.47:8086/write?db=telegraf: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
2018-06-04T03:58:15Z D! Output [influxdb] buffer fullness: 5059 / 5000 metrics.
2018-06-04T03:58:20Z E! [outputs.influxdb]: when writing to [http://172.16.11.47:8086]: Post http://172.16.11.47:8086/write?db=telegraf: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
2018-06-04T03:58:20Z E! Error writing to output [influxdb]: could not write any address
2018-06-04T03:58:25Z E! [outputs.influxdb]: when writing to [http://172.16.11.47:8086]: Post http://172.16.11.47:8086/write?db=telegraf: read tcp 172.16.11.48:58328->172.16.11.47:8086: wsa


#4

I’m not sure but you might need to look at metric buffer size.

2018-06-04T03:58:15Z D! Output [influxdb] buffer fullness: 5059 / 5000 metrics.
I think you’ll need to adjust your configuration to fix this.


#5

Your Telegraf instance is not able to communicate with your InfluxDB instance. There could be many reasons for this, you will need to investigate. Some good places to start are testing your network and looking at the load on your InfluxDB server.

The metrics buffer is likely filling up because Telegraf cannot write points to InfluxDB. Changing the size of the buffer probably won’t help.

Again, you need to provide more detail in order for someone to help you with this issue. What does your installation look like? How many machines, what operating system, are they in the cloud? What metrics are you collecting? How frequently? What troubleshooting steps have you already tried?


#6

I have this same problem. The telegraf and influx are installed on the same machine, that is, it is not a firewall. SELinux is disabled. And yet, it does not communicate.

2018-12-27T13:40:15Z E! [outputs.influxdb] when writing to [https://10.13.0.245:8086]: Post https://10.13.0.245:8086/write?db=telegraf: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
2018-12-27T13:40:15Z D! [outputs.influxdb] buffer fullness: 18112 / 60000 metrics.
2018-12-27T13:40:15Z E! [agent] Error writing to output [influxdb]: could not write any address

Influx conf:

[http]
#enabled = true
bind-address = “0.0.0.0:8086”
auth-enabled = true
realm = “InfluxDB”

Telegraf conf:

urls = [“https://10.13.0.245:8086”]
database = “telegraf”
skip_database_creation = true
timeout = “15s”

HTTP Basic Auth

username = “username”
password = “password”

load average: 0.20, 0.21, 0.24


#7

As I mentioned before, there could be many reasons for this, you will need to investigate. In your case I would start by testing the network. Are you able to make a connection using that IP address and port and a tool like netcat? You can start an instance of netcat that listens on 0.0.0.0:8086 and another instance that connects to 10.13.0.245:8086 to verify that you are able to make a TCP connection.

Is there a reason you’re not using 127.0.0.1 or localhost to connect, since the applications are on the same machine?