Giters

seaweedfs / seaweedfs

SeaweedFS is a fast distributed storage system for blobs, objects, files, and data lake, for billions of files! Blob store has O(1) disk seek, cloud tiering. Filer supports Cloud Drive, cross-DC active-active replication, Kubernetes, POSIX FUSE mount, S3 API, S3 Gateway, Hadoop, WebDAV, encryption, Erasure Coding.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

start iam server with docker, request always response 500

zuzuviewer opened this issue · comments

commented
  1. docker pull chrislusf/seaweedfs:3.64
  2. create /opt/seaweedfs/config.json file and write "{}"
  3. docker run --network=host -v /opt/seaweedfs/config.json:/etc/iam/identity.json chrislusf/seaweedfs:3.64 server -s3 -s3.config=/etc/iam/identity.json
  4. docker run --network=host chrislusf/seaweedfs:3.64 iam
  5. curl -X POST http://localhost:8111/?Action=ListAccessKeys
  6. request response InternalError
commented

Show error 500 message in logs.
Also not sure if this is the correct request, it seems either POST with body or GET with uri parameters

curl -X POST http://localhost:8111/?Action=ListAccessKeys
commented

Show error 500 message in logs. Also not sure if this is the correct request, it seems either POST with body or GET with uri parameters

curl -X POST http://localhost:8111/?Action=ListAccessKeys

no any log output in iam service and seaweedfs service.

listAccessKeys Doc. And I think POST request is no problem without body.
Also not just this one request response 500. All Iam request response 500.

commented

Maybe iam service has a lot of bug. If someone create user,access_key,secret_key by weed shell s3.configure, iam service don't know it and it will reject right user request. And identity is from s3.config startup parameter or filer store, this is difficult to use, when identity from s3.config startup parameter, how to curd iam and valid forever, if restart, serivce will only read identity from s3.config, or update filer identity store, it will override s3.config in cache.