Hi there, I didn’t find anybody having this issue, so let’s see if somebody can help me.
I’ve been working with InfluxDB v2 for some time, and I wanted to try InfluxDB v3.
In order to try it in a clean environment. I created a VM, Ubuntu 24.04.2, 50Gb, typical configuration I do to try this kind of stuff.
Problem:
The script fails during the download phase with curl error code (23), indicating a write error. This happens for both the main tarball and the SHA256 checksum file.
Error Output:
Downloading InfluxDB 3 Core to /home/jam/.influxdb
mkdir -p '/home/jam/.influxdb'
curl -sSL 'https://dl.influxdata.com/influxdb/releases/influxdb3-core-3.0.3_linux_amd64.tar.gz' -o '/home/jam/.influxdb/influxdb3-core.tar.gz'
curl: (23) client returned ERROR on write of 8192 bytes
Verifying '/home/jam/.influxdb/influxdb3-core.tar.gz'
curl -sSL 'https://dl.influxdata.com/influxdb/releases/influxdb3-core-3.0.3_linux_amd64.tar.gz.sha256' -o '/home/jam/.influxdb/influxdb3-core.tar.gz.sha256'
curl: (23) client returned ERROR on write of 106 bytes
cut: /home/jam/.influxdb/influxdb3-core.tar.gz.sha256: No such file or directory
Could not find properly formatted SHA256 in '/home/jam/.influxdb/influxdb3-core.tar.gz.sha256'. Aborting.
Troubleshooting Steps Taken:
-
Confirmed sufficient disk space.
-
The mkdir -p ‘/home/jam/.influxdb’ command within the script (and when run manually as user jam) succeeds without issues. My user jam owns /home/jam and its subdirectories.
-
Manually executing the curl command to download the tarball directly to /home/jam/.influxdb/ (as user jam) also fails with the same curl: (23) client returned ERROR on write… error:
Contrasting Success:
Interestingly, I was able to successfully install InfluxDB v3 using the exact same script and process within WSL (Windows Subsystem for Linux) on the same host machine without any errors. This suggests the issue is specific to my Ubuntu 24.04 VM environment.
In this case, I see influxdb3 running in port 8181, but the terminal doesn’t find the command “influxdb3”.
Question:
Does anyone have insights into what might be causing curl to fail with a write error (23) specifically within this Ubuntu 24.04 VM environment, even when mkdir to the same target path works and general permissions/disk space seem fine? Could it be related to a specific curl version, a VM configuration peculiarity, or something else I might be overlooking?
And, in the WSL case, if somebody encountered the same “influxdb command not found” and knows how to solve it, that would be great.
Thanks for any help!