It goes into this loop while booting and never brings the API up.
What is the expected behavior?
That it boots :)
Additional details
After enabling debug output, I found that it goes into an endless loop with this:
{"name":"cardano-graphql","hostname":"cardano-graphql-75f8d6f79f-tjlnf","pid":1,"level":20,"msg":"Getting the most recent point with a new asset: Attempt 1 of 1001, retrying...","time":"2021-09-13T21:54:49.162Z","v":0}
I've checked the query that it's performed for that task and realised it returns empty results in this deployment:
I've tried restarting db-sync, hasura and ogmios also, just to see if there was some problem with any schema/table/view that would recover on restart, but no luck :(
It seems db might have been corrupted because of some graphql abrupt restart (I had some), but wanted to report the issue just in case.
It seems db-sync went a bit nuts, after restarting everything again it worked, so I'm assuming there was some other problem not related to graphql service itself. Closing!
Environment
I'm using official
cardano-graphql:5.1.0
andcardano-graphql-hasura:5.1.0
docker images.Platform
Platform version:
Runtime
Runtime version:
containerd
from Kubernetes):Steps to reproduce the bug
It goes into this loop while booting and never brings the API up.
What is the expected behavior?
That it boots :)
Additional details
After enabling debug output, I found that it goes into an endless loop with this:
I've checked the query that it's performed for that task and realised it returns empty results in this deployment:
While it works in other ones I have:
I've tried restarting db-sync, hasura and ogmios also, just to see if there was some problem with any schema/table/view that would recover on restart, but no luck :( It seems db might have been corrupted because of some
graphql
abrupt restart (I had some), but wanted to report the issue just in case.