-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Outputs.influxdb cannot write any address - error: EOF #7650
Comments
What InfluxDB server are you connecting to? is it a self-hosted one? If so, are there any matching error logs in InfluxDB? |
I have a few things I'd like to check into for this one around the json decoder and gzip handling. |
Right now we are having some issues on the server but it should be fixed soon. In the meanwhile you can leave instructions here, I will apply them asap |
@danielnelson sorry for the long wait, here are the info about my setup and configurations. Current configuration & setupThe setup
Client configurationVersion: Telegraf unknown (git: master 1b1382c) Server configuration (gateway)Version: Telegraf 1.14.2 (git: HEAD fb74eaf) Log since last Telegraf restart
I've noticed that the Telegraf gateway has an "old" version, I could start by updating it and check if the error persists. If you have something to try to get more data about the issue just let me know and I will configure/apply it as soon as possible |
I tried a few ideas I had to trigger the error, but wasn't successful in reproducing. I have a couple ideas for ways we could proceed though:
|
there will be lots of data passing by, I've never used Wireshark so far but it's not a problem to put it on the server sending metrics. Is there anything particular about it? |
Ideally we would limit the amount of data captured to capture only need the data directly around a single error. It would be good to have the log from Telegraf for the same time period so we can cross reference. Use a capture filter to limit the communication with the single server:
I'm not sure if HTTPS will be a issue here, it may not be possible to inspect the important part of the data with encryption in place but we can try without it first. |
I've tried Wireshark. I can get the encrypted data but I'm unable to decrypt them. If you don't have any additional suggestion I would consider adding some tracing code in telegraf itself in order to get the needed data. |
FYI: I had a similar error (EOF) when trying to run InfluxDB on Azure Container Instances. This turned out not to provide required storage performance, as it was using Azure Files/samba for the backend storage. Hence, a tip could be look into the backend storage for InfluxDB, and if possible test against a different instance using other storage. More details: |
I am going to close this issue. The issue has not had many updates in a while. While I know there have been reports of EOF errors coming up in the past, it can normally be traced to networking related issues. Users of the influxdb_v2 plugin have seen this for similar reasons. Additionally, we got a fix in upstream Go to better handle http2 connections where this was seen. |
I'm gathering data with telegraf and writing to a telegraf gateway (input influxdb_listener), sometimes I get the following error
I'm not sure about what can cause this, the telegraf gateway does not report any error.
I've found an old issue #2280 about the same error and tried to change several settings to solve this but without luck.
Telegraf gatherer conf
metric_batch_size
- in case there was too much datainterval
- to give more time to the outputcontent_encoding = "gzip"
- to reduce the request body sizetimeout
- to give it more timeTelegraf gateway conf
max_body_size
- doubled its sizemax_body_size = "64MiB"
Relevant telegraf.conf:
# Full conf to be added (the server is offline now), but there is nothing special in the conf itself
System info:
Steps to reproduce:
I doubt this will be easy to replicate but here are the steps
Expected behavior:
Not getting the error
EOF
errorActual behavior:
Additional info:
The text was updated successfully, but these errors were encountered: