Skip to content
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 connect to s3 minio #98

Open
3 tasks done
cabiamdos opened this issue Apr 22, 2024 · 4 comments
Open
3 tasks done

can't connect to s3 minio #98

cabiamdos opened this issue Apr 22, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@cabiamdos
Copy link

Have you read a contributing guide?

  • I have read CONTRIBUTING.md
  • I have searched the existing issues and didn't find any that were similar
  • I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

I can't connect the filenode to s3 bucket

Expected Behavior

expected to connect to minio s3 storage

Steps To Reproduce

git clone https://github.com/anyproto/any-sync-filenode/
cd any-sync-filenode
make deps
make build
cd bin
./any-sync-filenode -c /path/to/file_1.yml

the s3Store section of the file_1.yml

s3Store:
    endpoint: http://127.0.0.1:9000
    bucket: any-sync-files
    region: eu-central-1
    profile: default
    maxThreads: 16
    credentials:
      accessKey: <access_key>
      secretKey: <secret_key>
    forcePathStyle: true

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

s3Store:
    endpoint: http://127.0.0.1:9000
    bucket: any-sync-files
    region: eu-central-1
    profile: default
    maxThreads: 16
    accessKey: <access_key>
    secretKey: <secret_key>

when executing any-sync-filenode

./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

@cabiamdos cabiamdos added the bug Something isn't working label Apr 22, 2024
@subatiq
Copy link

subatiq commented Apr 25, 2024

There is also indexBucket field in the config. It seems it's not autogenerated, yet required. Here is an example

@fb929
Copy link
Contributor

fb929 commented Apr 26, 2024

@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
Copy link
Author

y

There is also indexBucket field in the config. It seems it's not autogenerated, yet required. Here is an example

Yes I end up fixing by hardcoding this values in the code; and then compiling it.

@cabiamdos
Copy link
Author

@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.

I haven't find this puppet any sync on the documentatation (https://tech.anytype.io/how-to/self-hosting). I will take a look at this anyways, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants