Hello All,
I have set the mimir on my Linux machine where I am not able to able to connect to S3 bucket however when I run the AWS S3 command which is running fine and able to list and copy the object but it is not working through mimir.
Mimir platform and version.
Mimir, version 2.12.0 (branch: release-2.12, revision: c7aab9e03)
go version: go1.21.8
platform: linux/amd64
Error message -
ts=2024-04-15T03:15:34.106998862Z caller=module_service.go:72 level=debug msg=“module waiting for initialization” module=memberlist-kv waiting_for=sanity-check
ts=2024-04-15T03:15:34.106954635Z caller=module_service.go:72 level=debug msg=“module waiting for initialization” module=querier waiting_for=sanity-check
ts=2024-04-15T03:15:34.107016975Z caller=module_service.go:72 level=debug msg=“module waiting for initialization” module=ruler waiting_for=sanity-check
ts=2024-04-15T03:15:34.107055172Z caller=sanity_check.go:32 level=info msg=“Checking directories read/write access”
ts=2024-04-15T03:15:34.107003081Z caller=module_service.go:72 level=debug msg=“module waiting for initialization” module=ingester-ring waiting_for=memberlist-kv
ts=2024-04-15T03:15:34.107061632Z caller=module_service.go:72 level=debug msg=“module waiting for initialization” module=store-queryable waiting_for=memberlist-kv
ts=2024-04-15T03:15:34.107297987Z caller=sanity_check.go:37 level=info msg=“Directories read/write access successfully checked”
ts=2024-04-15T03:15:34.107305065Z caller=sanity_check.go:39 level=info msg=“Checking object storage config”
ts=2024-04-15T03:15:34.243894005Z caller=sanity_check.go:115 level=warn msg=“Unable to successfully connect to configured object storage (will retry)” err=“blocks storage: unable to successfully send a request to object storage: No message”
ts=2024-04-15T03:15:34.245948937Z caller=seed.go:127 level=warn msg=“failed to read cluster seed file from object storage” err=“No message”
ts=2024-04-15T03:15:35.612020768Z caller=seed.go:127 level=warn msg=“failed to read cluster seed file from object storage” err=“No message”
ts=2024-04-15T03:15:35.959905597Z caller=sanity_check.go:115 level=warn msg=“Unable to successfully connect to configured object storage (will retry)” err=“blocks storage: unable to successfully send a request to object storage: No message”
ts=2024-04-15T03:15:38.154669759Z caller=sanity_check.go:115 level=warn msg=“Unable to successfully connect to configured object storage (will retry)” err=“blocks storage: unable to successfully send a request to object storage: No message”
ts=2024-04-15T03:15:38.671459255Z caller=seed.go:127 level=warn msg=“failed to read cluster seed file from object storage” err=“No message”
ts=2024-04-15T03:15:42.451714571Z caller=sanity_check.go:115 level=warn msg=“Unable to successfully connect to configured object storage (will retry)” err=“blocks storage: unable to successfully send a request to object storage: No message”
ts=2024-04-15T03:15:43.649066306Z caller=seed.go:127 level=warn msg=“failed to read cluster seed file from object storage” err=“No message”
ts=2024-04-15T03:15:46.64013837Z caller=sanity_check.go:115 level=warn msg=“Unable to successfully connect to configured object storage (will retry)” err=“blocks storage: unable to successfully send a request to object storage: No message”
ts=2024-04-15T03:15:50.846614752Z caller=sanity_check.go:115 level=warn msg=“Unable to successfully connect to configured object storage (will retry)” err=“blocks storage: unable to successfully send a request to object storage: No message”
ts=2024-04-15T03:15:54.697504563Z caller=seed.go:127 level=warn msg=“failed to read cluster seed file from object storage” err=“No message”
ts=2024-04-15T03:15:55.437310149Z caller=sanity_check.go:115 level=warn msg=“Unable to successfully connect to configured object storage (will retry)” err=“blocks storage: unable to successfully send a request to object storage: No message”
ts=2024-04-15T03:16:00.19390413Z caller=sanity_check.go:115 level=warn msg=“Unable to successfully connect to configured object storage (will retry)” err=“blocks storage: unable to successfully send a request to object storage: No message”
ts=2024-04-15T03:16:05.187345259Z caller=sanity_check.go:115 level=warn msg=“Unable to successfully connect to configured object storage (will retry)” err=“blocks storage: unable to successfully send a request to object storage: No message”
Mimir yaml file -
Do not use this configuration in production.
It is for demonstration purposes only.
multitenancy_enabled: false
blocks_storage:
backend: s3
s3:
endpoint: xxxxxx
bucket_name: xxxxx
secret_access_key: “${AWS_SECRET_ACCESS_KEY}” # This is a secret injected via an environment variable
access_key_id: “${AWS_ACCESS_KEY_ID}” # This is a secret injected via an environment variable
region: xxxxx
ruler_storage:
backend: filesystem
filesystem:
dir: /home/store/mimir/rules
compactor:
data_dir: /home/store/mimir/mimir/compactor
sharding_ring:
instance_interface_names: [“eth1”]
kvstore:
store: memberlist
distributor:
ring:
instance_addr: x.x.x.x
instance_interface_names: [“eth1”]
kvstore:
store: memberlist
ingester:
ring:
instance_addr: x.x.x.x
instance_interface_names: [“eth1”]
kvstore:
store: memberlist
replication_factor: 1
server:
http_listen_port: 9091
log_level: debug
ruler:
ring:
instance_interface_names: [“eth1”]
store_gateway:
sharding_ring:
instance_interface_names: [“eth1”]
replication_factor: 1
Thanks !!