Call to /api/v2/write yields 500 internal server error due to timeout

InfluxDB 2
1

Hello,

I have recently installed influxdb v2 on my server. I’ve had no issues during the set-up, but have encountered errors testing it.

I first encountered an error going through the setup on the website where it told me to run:

influx write --bucket sample-bucket --url https://influx-testdata.s3.amazonaws.com/air-sensor-data-annotated.csv

The command yielded a 500 internal server error, but the data was written (I checked via the Data Explorer in the Dashboard).

I didn’t think much of it and tried the example Python script. When writing, it hang for a bit and then crashed with the same error.

Finally, I tried using curl to try to find more info, but got none:

# curl "localhost:8087/api/v2/write?org=<MY_ORG>&bucket=<MY_BUCKET>&precision=ns" --header "Authorization: Token <MY_TOKEN>" --header "Content-Type: text/plain; charset=utf-8" --data-binary 'temp,id=X value=12.34'

{"code":"internal error","message":"unexpected error writing points to database: timeout"}

The behaviour is the same as with Python: curl runs, the data appears immediately in the Data Explorer, the command waits some time before it exits yielding the error response.

This is the result of influx version:

Influx CLI dev (git: a79a2a1b825867421d320428538f76a4c90aa34c) build_date: 2024-04-16T14:34:32Z

I’ve lost my mind yesterday thinking the data wasn’t written, but it WAS! That’s so weird…

2

I tried starting Influx using the influxd command and trying if that would work. Surprisingly it did!
That’s great, but I prefer running InfluxDB as a service. I simply reinstalled InfluxDB and everything worked. Magic!