graph-node icon indicating copy to clipboard operation
graph-node copied to clipboard

[Bug] Indexing stops for the specific subgraphs

Open steven94kr opened this issue 1 year ago • 0 comments

Bug report

  • Indexing stops for the specific subgraphs

We are using graph node for our L2 network using Optimism. But sometimes, the below error occurs and indexing is stopped for the specific subgraphs. I have never seen the error. How can I do to resolve the error?

You can see the indexing status using below query in here (https://graph-node.titan-sepolia.tokamak.network/graphql/playground)

{
  indexingStatuses(subgraphs: ["QmNa9YZ58oSRqjtFRNxufXpNTvJ5dRZAMn4nisRAPtL17y"]) {
    subgraph
    synced
    health
    paused
    node
    entityCount
    fatalError {
      handler
      message
      deterministic
      block {
        hash
        number
      }
    }
    nonFatalErrors {
      handler
      message
      deterministic
      block {
        hash
        number
      }
    }
    chains {
      chainHeadBlock {
        number
      }
      earliestBlock {
        number
      }
      latestBlock {
        number
      }
    }
  }
}

Thank you very much.

Relevant log output

Block stream produced a non-fatal error, error: block stream error missing field `block`, sgd: 37, subgraph_id: QmNa9YZ58oSRqjtFRNxufXpNTvJ5dRZAMn4nisRAPtL17y, component: SubgraphInstanceManager

IPFS hash

QmNa9YZ58oSRqjtFRNxufXpNTvJ5dRZAMn4nisRAPtL17y

Subgraph name or link to explorer

https://graph-node.titan-sepolia.tokamak.network/subgraphs/id/QmNYauo5HEKRrQuetjAzPbLE57tcsSu5swzwcPHM6d5PyC

Some information to help us out

  • [ ] Tick this box if this bug is caused by a regression found in the latest release.
  • [ ] Tick this box if this bug is specific to the hosted service.
  • [X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None

steven94kr avatar Oct 15 '24 05:10 steven94kr