After starting Influxdb it works for a while, then completely stops working with queries or data point ingest, timing out the http endpoint. InfluxDB console reports messages like this :
ts=2023-07-11T12:01:27.527233Z lvl=warn msg="internal error not returned to client" log_id=0iy3ZWxG000 handler=error_logger error="context canceled"
It seems to stall during ingest requests performed from go client with 10 threads in synchronous writes, which doesn’t seem to be that much.
Only solution is to restart InfluxDB.
This is running 2.7.1 as container on my workstation or on a Kubernetes cluster.
As InfluxDB isn’t logging anything useful really, not sure where to start to troubleshoot this.
This is a docker deployment so I don’t think there is a point reinstalling.
I’m running flux queries in grafana while importing metrics indeed, it’s possible influxdb crashes only when doing those refresh in Grafana.
If Influxdb randomly crashes on Flux queries, I guess it’s not going to work for me
@Anaisdg I’m facing this issue but not on all queries, I’m making a query that uses a reduce fro 90 days, and the only thing I get from the influx query execution is Failed to execute Flux query
and in the K8s nide logs I’m just getting ts=2024-11-05T11:43:22.710906Z lvl=warn msg="internal error not returned to client" log_id=0sebx8mG000 handler=error_logger error="context canceled"
Logs from kotlin client in the header are saying this
Exact same problem here (same error message).
It was running fine for many months with 2.7.3 (via docker and used by OpenHAB as it’s persistence service). From one day to the next this error occurs, but just for some queries.
Also an upgrade to 2.7.10 has not fixed the issue.
