New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weedfs won't work without any reason #2146
Comments
seems like the volume file is not present on the filer directory. how did you start your weedfs instance? |
They were working correctly for 3 months, today suddenly weed baceame unhealthy, |
Its okay don't worry be patient. how did you start your seaweedfs instance? the command? are you in docker? are you in systemctl job? can you see the logs? |
restart the volume server(s)? |
These are my log:
and ` ` and some part of logs said: response method:GET : ` ` |
No I restart all Masters |
I'm using systemctl job Command to run weed cluster in systemd unit file: weed version: |
These are just part of my weed cluster logs , because they were repetitive so I just copied the main part |
Added a possible fix. |
Hi,
Suddenly today I dont know , my weedfs cluster became unhealthy,
There is some Errors that I would attach but I dont know how should I fix this issue.
I would appreciate if you could help me to solve the problem: @chrislusf
I have restarted master but it didn't have any effect
weed version:
version 8000GB 2.40 e983f91 linux amd64
Jun 22 08:53:51 weed-master-1 seaweedfs-master[21217]: I0622 08:53:51 21217 common.go:53] response method:GET URL:/dir/lookup?volumeId=286 with httpStatus:404 and JSON:{"volumeId":"286","error":"volume id 286 not found"} Jun 22 08:53:51 weed-master-1 seaweedfs-master[21217]: I0622 08:53:51 21217 common.go:53] response method:GET URL:/dir/lookup?volumeId=926 with httpStatus:404 and JSON:{"volumeId":"926","error":"volume id 926 not found"} Jun 22 08:53:51 weed-master-1 seaweedfs-master[21217]: I0622 08:53:51 21217 common.go:53] response method:GET URL:/dir/lookup?volumeId=22 with httpStatus:404 and JSON:{"volumeId":"22","error":"volume id 22 not found"}
The text was updated successfully, but these errors were encountered: