-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Can't upload on s3 bucket. #1631
Comments
Here is debug log:
|
please show weed logs |
|
Need a log weed filer and weed filer volume with uploading file |
Sorry, where log? How can I enable logs? |
use param |
You are not configuring end point and are talking to aws directly. |
No. I configured endpoint. s3cmd woriking correctly with another bucket (created early) |
how did you configure the endpoint? I saw |
Thanks! I'm install seaweed as systemd service and use
What does it mean? I have a lot if free disk space. |
try set |
It was already set to How much is |
I have Nginx as proxy and balancer. It proxies requests to one of three filers (with s3). |
|
Each volume is configured to be 1GB. The folder You can reduce to If you are using the git master branch, to be released in 2.12, there is a more flexible configuration: If you have a lot of buckets to add, you can configure the per bucket storage this way in
This will add 1 physical volume when existing volumes are full. If using replication, you will need to add more volumes. See https://github.com/chrislusf/seaweedfs/wiki/Path-Specific-Configuration |
It's worked for me! Thanks Chris :) |
Hello!
Describe the bug
I've run seaweed with s3 (3 masters, 3 volumes, 3 filers on the same servers).
It works good.
Some time later I have a problem.
Create s3-bucket with s3cmd:
s3cmd mb s3://test
It succefully created.
That I tried to upload some file.
s3cmd put file s3://test
I've got error:
WARNING: Upload failed: /file (500 (InternalError): We encountered an internal error, please try again.)
But on older bucket I can upload files.
System Setup
/opt/seaweedfs/weed master -mdir=/data/seaweedfs/master -peers=10.214.3.19:9333,10.214.3.16:9333,10.214.3.17:9333 -volumeSizeLimitMB 1024
/opt/seaweedfs/weed volume -mserver=10.214.3.19:9333,10.214.3.16:9333,10.214.3.17:9333 -dir=/data/seaweedfs/volume -dataCenter dc1 -rack rack1 -ip=10.214.3.16 -max=0
/opt/seaweedfs/weed filer -master 10.214.3.19:9333,10.214.3.16:9333,10.214.3.17:9333 -s3 -s3.config /etc/seaweedfs/s3.config.json -s3.domainName example.com -s3.port 80
CentOS Linux release 7.8.2003 (Core)
weed version
version 30GB 2.11 98827d6 linux amd64
filer.toml
Here is part of filer.toml
Expected behavior
I can upload file to s3.
Additional context
Also I have the same problem with another s3 tools (aws, s3 sync)
The text was updated successfully, but these errors were encountered: