You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
where the access and secret key are generated in the web interface of the minio server, and the bucket is also created in the web interface. I have also tried with the URI s3://127.0.0.1:9000 and mc://127.0.0.1:9000, and
./any-sync-filenode
2024-04-22T11:47:07.676Z INFO common.nodeconf net configuration applie
{"netId": "N8eTyHkgv3o92TRXp437S5enToagceiFxe8U14MwDtAMC2Kt", "id": "66259cdc6b9da8546c62b438"}
2024-04-22T11:47:07.679Z INFO common.net.secure secure service i
{"peerId": "12D3KooWLRLdQKba9scB4KFVMiESn47VP7ZF2JWMPVRV5s9CDePs"}
2024-04-22T11:47:07.679Z ERROR app can't init service {"service": "common.commonfile.fileblockstore", "error": "s3 bucket is empty"}
2024-04-22T11:47:07.679Z FATAL main can't start app {"error": "can't init service 'common.commonfile.fileblockstore': s3 bucket is empty"}
Any ideas on how to fix this?
Thanks
Environment
- OS:ubuntu server
- Version: 20.04
Anything else?
it seems that the ./any-sync-filenode isn't reading the s3bucket configuration part
The text was updated successfully, but these errors were encountered:
@cabiamdos You need to create a file with access credentials.
Usually it's '$HOME/.aws/credentials'.
You can find an example configuration here and here.
@cabiamdos You need to create a file with access credentials. Usually it's '$HOME/.aws/credentials'. You can find an example configuration here and here.
Have you read a contributing guide?
Current Behavior
I can't connect the filenode to s3 bucket
Expected Behavior
expected to connect to minio s3 storage
Steps To Reproduce
the s3Store section of the file_1.yml
where the access and secret key are generated in the web interface of the minio server, and the bucket is also created in the web interface. I have also tried with the URI s3://127.0.0.1:9000 and mc://127.0.0.1:9000, and
when executing any-sync-filenode
Any ideas on how to fix this?
Thanks
Environment
Anything else?
it seems that the ./any-sync-filenode isn't reading the s3bucket configuration part
The text was updated successfully, but these errors were encountered: