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

problem applying hasura metadata: problem executing request (Client.Timeout exceeded while awaiting headers) #204

Closed
Konard opened this issue Apr 28, 2024 · 1 comment

Comments

@Konard
Copy link

Konard commented Apr 28, 2024

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?

@dbarrosop
Copy link
Member

dbarrosop commented Apr 29, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants