Failed to download files #9358
Answered
by
peterxcli
chehsunliu
asked this question in
FAQ
Failed to download files
#9358
-
|
I installed Ozone by Helm in my local MicroK8s in Ubuntu. The content of apiVersion: v2
name: ozone-stg
type: application
version: "0.1.0"
appVersion: "1.0.0"
dependencies:
- name: ozone
version: 0.2.0
repository: https://apache.github.io/ozone-helm-chartsThe pods appeared successfully: 
Then I connected to the shell of $ ozone sh bucket create s3v/my-bucket # SUCCESS
$ echo 123 > /tmp/a.txt # SUCCESS
$ ozone sh key put s3v/my-bucket/tmp/a.txt /tmp/a.txt # SUCCESS
$ ozone sh key ls s3v/my-bucket # SUCCESS
$ ozone sh key cat s3v/my-bucket/tmp/a.txt # FAILUREThe error of the command: It tested the port bash-5.1$ curl http://ozone-stg-datanode:9860
curl: (56) Recv failure: Connection reset by peer
bash-5.1$ curl http://ozone-stg-datanode-headless:9859
upstream connect error or disconnect/reset before headers. reset reason: protocol errorand bash-5.1$ netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:19864 0.0.0.0:* LISTEN 7/java
tcp 0 0 0.0.0.0:9886 0.0.0.0:* LISTEN 7/java
tcp 0 0 0.0.0.0:9882 0.0.0.0:* LISTEN 7/java
tcp 0 0 0.0.0.0:9858 0.0.0.0:* LISTEN 7/java
tcp 0 0 0.0.0.0:9859 0.0.0.0:* LISTEN 7/java
tcp 0 0 0.0.0.0:9856 0.0.0.0:* LISTEN 7/java
tcp 0 0 0.0.0.0:9857 0.0.0.0:* LISTEN 7/java
tcp 0 0 127.0.0.1:15000 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:15090 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:15021 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:15006 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:15001 0.0.0.0:* LISTEN -
tcp6 0 0 :::15020 :::* LISTEN - Not sure what else I can do for this situation. |
Beta Was this translation helpful? Give feedback.
Answered by
peterxcli
Nov 25, 2025
Replies: 1 comment 2 replies
-
|
It might be related to #8998 (comment) |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
The default setting is |
Beta Was this translation helpful? Give feedback.
-
|
That fix isn’t included in the 2.0 release yet. Since 2.1.0 release voting process is still in progress, there’s no official image that contains the fix. You can build the latest image from source by following: https://ozone-site-v2.staged.apache.org/docs/developer-guide/build/docker-images Then update your Helm chart to use that image — modify the image fields in values.yaml accordingly (see lines 17–20 here: https://github.com/peterxcli/ozone-helm-charts/blob/6c1a77be7c824a1dfabfdce7b55ecd680f924d7a/charts/ozone/values.yaml#L17-L20). |
Beta Was this translation helpful? Give feedback.
Answer selected by
jojochuang
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That fix isn’t included in the 2.0 release yet. Since 2.1.0 release voting process is still in progress, there’s no official image that contains the fix.
You can build the latest image from source by following: https://ozone-site-v2.staged.apache.org/docs/developer-guide/build/docker-images
Then update your Helm chart to use that image — modify the image fields in values.yaml accordingly (see lines 17–20 here: https://github.com/peterxcli/ozone-helm-charts/blob/6c1a77be7c824a1dfabfdce7b55ecd680f924d7a/charts/ozone/values.yaml#L17-L20).