Cardano-db-sync: Db-sync Error. Fails to index

Created on 22 Nov 2020  ·  11Comments  ·  Source: input-output-hk/cardano-db-sync

Hi I am running cardano-db 6.0.0 with cardan-node1.21.1. Suddenly it failed to sync new blocks with such error:

Nov 21 23:05:35 cardano-fork cardano-db6[1971]: [db-sync-node.ErrorPolicy:Error:4] [2020-11-21 23:05:35.51 UTC] [String "ErrorPolicyUnhandledApplicationException Panic! applyHeaderTransition failed: [[NewEpochFailure (EpochFailure (NewPpFailure (UnexpectedDepositPot (Coin 857622000000) (Coin 857626000000))))]]\nCallStack (from HasCallStack):\n  error, called at src/Shelley/Spec/Ledger/API/Validation.hs:92:15 in shelley-spec-ledger-0.1.0.0-inplace:Shelley.Spec.Ledger.API.Validation",String "ErrorPolicyTrace",String "LocalAddress {getFilePath = \"state-node-mainnet/sock\"}"]
Nov 21 23:05:39 cardano-fork cardano-db6[1971]: [db-sync-node.Handshake:Info:81401] [2020-11-21 23:05:39.94 UTC] [String "Send (ClientAgency TokPropose,MsgProposeVersions (fromList [(NodeToClientV_1,TInt 764824073),(NodeToClientV_2,TInt 764824073),(NodeToClientV_3,TInt 764824073)]))",String "LocalHandshakeTrace",String "ConnectionId {localAddress = LocalAddress {getFilePath = \"\"}, remoteAddress = LocalAddress {getFilePath = \"state-node-mainnet/sock\"}}"]
Nov 21 23:05:39 cardano-fork cardano-db6[1971]: [db-sync-node.Handshake:Info:81401] [2020-11-21 23:05:39.94 UTC] [String "Recv (ServerAgency TokConfirm,MsgAcceptVersion NodeToClientV_3 (TInt 764824073))",String "LocalHandshakeTrace",String "ConnectionId {localAddress = LocalAddress {getFilePath = \"\"}, remoteAddress = LocalAddress {getFilePath = \"state-node-mainnet/sock\"}}"]

Most helpful comment

This is a duplicate of #398 .

Applied your commit with tag tmp-fix-6.0.x but unfortunately it didn't help

That only helps with nodes that aren't already affected. Quote from the comment:

However, running this version may detect an already corrupted ledger state (I am not even sure what that would look like) in which case a resync will be required.

All 11 comments

This is a duplicate of #398 .

This is a duplicate of #398 .

Applied your commit with tag tmp-fix-6.0.x but unfortunately it didn't help

This is a duplicate of #398 .

Applied your commit with tag tmp-fix-6.0.x but unfortunately it didn't help

That only helps with nodes that aren't already affected. Quote from the comment:

However, running this version may detect an already corrupted ledger state (I am not even sure what that would look like) in which case a resync will be required.

Thanks for the information.
So any choices to make an indexer work now?

So any choices to make an indexer work now?

Sorry, what? I do not even understand what you are asking.

Can you give me a piece of advice how to make cardano-db-sync work now, after such failure,please?

Thanks for the information.
So any choices to make an indexer work now?

You'll need to do a re-sync.

And if you are not running it in Docker then

PGPASSFILE=config/pgpass-mainnet scripts/postgresql-setup.sh --recreatedb

@alexqrid If you have managed to get the fixed version running and re-synced your db, please close this.

Just downgraded to cardano-db-sync 5.0.3 and synced from scratch. Everything seems to work fine.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

erikd picture erikd  ·  3Comments

rcmorano picture rcmorano  ·  6Comments

dmitrystas picture dmitrystas  ·  28Comments

xdzurman picture xdzurman  ·  12Comments

erikd picture erikd  ·  10Comments