[weed mount] write file error #1639
Comments
|
add more log volume: master: master and volume logs seem to be ok |
|
can you try the config.yaml in this page? https://github.com/chrislusf/seaweedfs/wiki/Harbor-with-SeaweedFS |
still error： push process: stucked, can't push success |
|
Added a fix a102157 Please try maybe 15 minutes later with |
seems doesn't work |
|
please show the full logs. |
|
wait, when |
filer: volume: master: weed mount(use 2.12 release version executable binary |
use this version build executable |
|
I found that although I successfully pushed the image, there are some logs on filer and weed mount contained： filer full log: weed mount full log: I want to know whether the above logs, such as |
|
No. |
when i setup seaweed in k8s，use this version. Pushing the image still get stuck. when i push image, master、volume and weed mount did not output logs, only filer outputs the following log : |
|
Can not help without details. Do you want to share your k8s setup details? |
|
totoal: 1 master pod、 1 filer pod、 1 volume pod、1 master svc、1 filer svc、 2 volume svc(1 headless and 1 nodeport) detail info kubectl describe pod seaweedfs-master-0: kubectl describe pod seaweedfs-volume-0 $publicurl=10.10.10.215:32605 (10.10.10.215 is k8s master node's ip, 32605 is port exposed by nodeport volume svc ) kubectl describe svc seaweedfs-filer: kubectl describe svc seaweedfs-master kubectl describe svc seaweedfs-volume kubectl describe svc seaweedfs-volume-0-external l try again, after setup seaweedfs in k8s , only the filer outputs the logs when i push the image for the first time. What's more, when I execute the push the image command, the filer will immediately print the following log： After the first push image failed，try to push image several times, still failed, and there are no logs output. |
|
In k8s, when I set the port of publicUrl and nodePort of external as 8080, the image can be pushed successfully. The Then I tested the seaweedfs installed in docker with the version you fixed:
And i found that once the port of volume and publicUrl are changed to non-8080, there is still a problem with pushing the image.
So there may be something wrong with port 8080 or pubilcUrl |
use corresponding grpc port. |
|
It works. And I tested in K8s, I found that port in volume server's If I setup multiple volume servers, it means I need to start the volume servers with different ports. Now k8s does not support obtaining pod id in statefulset: kubernetes/kubernetes#40651, so it is difficult to start multiple volume servers with different ports. So I want to know if the system can be optimized to close the association between the port of |
|
Can you try https://github.com/seaweedfs/seaweedfs-operator ? It should do everything for you. If not, please help to fix it. |
|
ok, I will try seaweedfs-operator. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
after weed mount, write file to filesystem, get error（filer‘s log）:
The error in the last line above appears many many times
System Setup
version 2.12
seaweedfs-compose.yml:
docker-registry-config.yml:
run:
Expected behavior
write file success to filesystem from
weed mountAdditional context
1、
docker pull nginx:latest2、
docke tag nginx:latest 127.0.0.1:5001/nginx:latest3、
docker push 127.0.0.1:5001/nginx:latestThe upload process is stuck，can not finish push
This error just likes #1609, but this time docker registry backend use filesystem from
weed mountThe text was updated successfully, but these errors were encountered: