Hellot there,
I want to test the stack InfluxDB/Telegraf/Grafana for multi site monitoring and this is my test configuration :
Logs on Telegraf > https://pastebin.com/raw/qsD1xZNG
Despite having been searching for hours to do, I can not find the parameter for my two Telegraf nodes to write in the InfluxDB DBs.
Could this be related to Proxy?
opened 01:12PM - 26 Oct 17 UTC
closed 05:54AM - 27 Oct 17 UTC
discussion
## Bug report
Hi. First of all, thanks a lot for your support and the tool!
I'… ve a problem with latest telegraf versions (1.4.2 and 1.4.3), tryining to write into influxdb (1.3.6).
I've tested also with a previous version (telegraf 1.2.1) in windows and linux machines and it works perfectly
### Relevant telegraf.conf:
```
[agent]
interval = "10s"
round_interval = true
metric_buffer_limit = 1000
flush_buffer_when_full = true
collection_jitter = "0s"
flush_interval = "10s"
flush_jitter = "0s"
[[outputs.influxdb]]
urls = ["http://10.19.24.123:8086"]
database = "telegraf" # required
precision = "s"
timeout = "5s"
```
### System info:
- Suse Linux 12
- Windows 8
Telegraf 1.4.3 and 1.4.2
### Steps to reproduce:
1. Start a clean installation of influxdb
2. Configure and start telegraf
### Expected behavior:
Metrics stored into influxdb
### Actual behavior:
```
2017-10-26T11:52:10Z E! InfluxDB Output Error: Response Error: Status Code [403]
, expected [204], [<nil>]
2017-10-26T11:52:10Z E! Error writing to output [influxdb]: Could not write to a
ny InfluxDB server in cluster
```
### Additional info:
[Include gist of relevant config, logs, etc.]
There's a corporate proxy, but everything works with telegraf 1.2.1
### Use case:
POC in order to show to managers and OPS team the advantages of gathering metrics and alerting using the stack (chronograf, telegraf , kapacitor)
Thanks again!
I applied the solution of this post, but it did not change anything.
In the GitHub issue linked to above, the server is returning a 403 response.
The Telegraf logs @chapelle shared indicate that Telegraf cannot connect to InfluxDB at all.
This is most often a networking issue. Did you verify that you are able to connect from 10.0.0.1 and 10.0.0.2 to 10.0.0.254 over port 8086? You can test this using a tool like netcat .
It was indeed a problem with firewalld.
Sorry for the loss of time and thanks for your answers.
No problem! We’re here to help.
