Closed puneet-khushwani-eth closed 5 years ago
@puneet-khushwani-eth Hi, sorry you're having this issue, could you provide instructions to reproduce this?
from our repo https://github.com/mosaicdao/mosaic-chains, you can run either of the below commands:
npm run test:smoke:goerli
npm run test:smoke:ropsten
they would internally spawn processes which would host the-graph server and its dependencies. We then deploy dub graph and verify its deployment.
To see crash logs of the graph docker process you can use the following command
docker logs --follow mosaic_graph_goerli_graph-node_1
@puneet-khushwani-eth Thanks for the instructions, I've reproduced it. What happened is that we were previously allowing a configuration that's really unsupported, which is to have ETHEREUM_REORG_THRESHOLD be larger than the chain. Than env var defaults to 50, and in your case your chain size is 0 from what I can tell, so you can fix this by setting ETHEREUM_REORG_THRESHOLD=0
. Please let me know if that works for you!
What is the current behavior?
Our process starts docker containers for graph-node (with a fresh data directory) and its dependencies. To this we deploy a sub-graph and then fire some calls to it to verify if deployment was successful. In most cases the docker process for graph-node gets killed abruptly (some times even before we start deploying sub-graph)
Versions we use - docker compose : 1.23.2 geth : 1.9.5 the-graph : 0.16.0
logs we see:
What is the expected behavior?
docker process should be running and we should be able to make calls to the server