problem applying hasura metadata: problem executing request (Client.Timeout exceeded while awaiting headers)
Konard opened this issue · comments
At deep-foundation/hasura#19 we found a problem with nhost/hasura-storage:0.2.3:
Logs are repeating only these lines:
time="2024-04-28T13:19:24Z" level=info msg="applying hasura metadata"
time="2024-04-28T13:19:34Z" level=error msg="problem applying hasura metadata: problem adding metadata for the buckets table: problem executing request: Post \"http://host.docker.internal:8080/v1/metadata\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
problem reading : Config File "hasura-storage" Not Found in "[/]"
time="2024-04-28T13:19:35Z" level=info msg="storage version 0.2.3"
time="2024-04-28T13:19:35Z" level=debug msg=parameters bind=":8000" debug=true hasura-endpoint="http://host.docker.internal:8080/v1" hasura-metadata=true postgres-migrations=false s3-bucket=default s3-endpoint="http://host.docker.internal:9000" s3-region=no-region s3-root-folder=default trusted-proxies="[]"
Do you have an idea on why there might be timeout exceeded? And how to diagnose and fix such problem?
This looks like a problem with your self-hosted setup so you will have to check how you set things up and ensure that your connectivity works fine. Also, keep in mind 0.2.3 is ancient.
Closing as this does not look like an issue with hasura-storage.