Hasura graphql-engine server does not start properly on local environment after version 2.17.1 #9676
Replies: 4 comments 1 reply
-
Looks like the first line of the logs is "gracefully shutting down server":
This implies there's more logs beforehand that we're not seeing. Can you share them? In addition, it seems you're using a custom Docker image that runs HGE: |
Beta Was this translation helpful? Give feedback.
-
Hi Samir, here is the docker file:
I did checked and the docker entry point is similar just a few extra logging. The logs (all of it since all looks good to me, but truncated at the end since it's only logs of the seeds for pages):
|
Beta Was this translation helpful? Give feedback.
-
It looks like you haven't added the CMD graphql-engine \
--metadata-database-url $METADATA_DATABASE_URL \
serve \
--server-port $PORT \
--enable-console Please take a look at the README for more info. This information should also be in the docs but seems to be missing. I will bring it up with the Hasura documentation team. |
Beta Was this translation helpful? Give feedback.
-
Hi Samir,
is not working as described here: https://hasura.io/docs/latest/deployment/graphql-engine-flags/reference/#server-port My local environment does work if I just replace the:
|
Beta Was this translation helpful? Give feedback.
-
Hi all,
We are using hasura in production and currently the cloud version is at [v2.25.1-cloud.1], but we didn’t manage to keep up to date with our local development environment where we did get stuck to version 2.17.1 (hasura/graphql-engine:v2.17.1.cli-migrations-v3). The reason is that any newer version just cannot start properly even if we did not change anything in our docker compose yaml file:
In the logs didn't find anything suspicious, the last thing logged is an invocation of the cron trigger, so it looks like will start, but then it just stops..
Any idea how to fix this?
Thanks in advance,
Maria
Beta Was this translation helpful? Give feedback.
All reactions