Errore: "hash incoerente". I lavoratori vanno in crash e il nodo non riesce a connettersi agli altri

Question

Errore: "hash incoerente". I lavoratori vanno in crash e il nodo non riesce a connettersi agli altri

5

238 2019-03-17

Ricevo costantementei seguentierrori. Ciò che spicca è l'errore "hashincoerente",che apparentemente causail crash dei lavoratori. L'hash dell'intestazione delbloccoe quello dell'hash locale sembrano differire. Non hoidea di cosa significhiperò. Qualcuno sa come risolvere questoproblema?

 Mar 17 15:14:35 - node.validator.bootstrap_pipeline: Unexpected error (validator):
Mar 17 15:14:35 - node.validator.bootstrap_pipeline: Error:
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:   Inconsistent hash:
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:     local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:     block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq
Mar 17 15:14:35 - node.validator.bootstrap_pipeline: 
Mar 17 15:14:35 - validator.peer(151): Worker crashed [NetXdQprcVkpa:idsMwfkFJFTX]:
Mar 17 15:14:35 - validator.peer(151): Inconsistent hash:
Mar 17 15:14:35 - validator.peer(151):   local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
Mar 17 15:14:35 - validator.peer(151):   block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq
Mar 17 15:14:35 - validator.peer(152): Worker started for NetXdQprcVkpa:idrhpgmWuEDG
Mar 17 15:14:35 - validator.block: Validation of block BLqhrPaH6WQtVYZssbonME7DPiQLTvZyidkYa8dvAxxoeTsnVKD failed
Mar 17 15:14:35 - validator.block: Pushed: 2019-03-17T15:14:35Z, Treated: 2019-03-17T15:14:35Z, Failed: 2019-03-17T15:14:35Z
Mar 17 15:14:35 - validator.block: Inconsistent hash:
Mar 17 15:14:35 - validator.block:   local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
Mar 17 15:14:35 - validator.block:   block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq
Mar 17 15:14:35 - node.validator.bootstrap_pipeline: Unexpected error (validator):
Mar 17 15:14:35 - node.validator.bootstrap_pipeline: Error:
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:   Inconsistent hash:
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:     local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:     block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq
Mar 17 15:14:35 - node.validator.bootstrap_pipeline: 
Mar 17 15:14:35 - validator.peer(152): Worker crashed [NetXdQprcVkpa:idrhpgmWuEDG]:
Mar 17 15:14:35 - validator.peer(152): Inconsistent hash:
Mar 17 15:14:35 - validator.peer(152):   local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
Mar 17 15:14:35 - validator.peer(152):   block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq

I'm consistently getting the below errors. What stands out is the "inconsistent hash" error, seemingly causing the workers to crash. The hash of the block header and this of the local hash seem to differ. I have no idea what this means though. Does anyone know how to solve this issue?

Mar 17 15:14:35 - node.validator.bootstrap_pipeline: Unexpected error (validator):
Mar 17 15:14:35 - node.validator.bootstrap_pipeline: Error:
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:   Inconsistent hash:
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:     local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:     block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq
Mar 17 15:14:35 - node.validator.bootstrap_pipeline: 
Mar 17 15:14:35 - validator.peer(151): Worker crashed [NetXdQprcVkpa:idsMwfkFJFTX]:
Mar 17 15:14:35 - validator.peer(151): Inconsistent hash:
Mar 17 15:14:35 - validator.peer(151):   local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
Mar 17 15:14:35 - validator.peer(151):   block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq
Mar 17 15:14:35 - validator.peer(152): Worker started for NetXdQprcVkpa:idrhpgmWuEDG
Mar 17 15:14:35 - validator.block: Validation of block BLqhrPaH6WQtVYZssbonME7DPiQLTvZyidkYa8dvAxxoeTsnVKD failed
Mar 17 15:14:35 - validator.block: Pushed: 2019-03-17T15:14:35Z, Treated: 2019-03-17T15:14:35Z, Failed: 2019-03-17T15:14:35Z
Mar 17 15:14:35 - validator.block: Inconsistent hash:
Mar 17 15:14:35 - validator.block:   local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
Mar 17 15:14:35 - validator.block:   block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq
Mar 17 15:14:35 - node.validator.bootstrap_pipeline: Unexpected error (validator):
Mar 17 15:14:35 - node.validator.bootstrap_pipeline: Error:
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:   Inconsistent hash:
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:     local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
Mar 17 15:14:35 - node.validator.bootstrap_pipeline:     block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq
Mar 17 15:14:35 - node.validator.bootstrap_pipeline: 
Mar 17 15:14:35 - validator.peer(152): Worker crashed [NetXdQprcVkpa:idrhpgmWuEDG]:
Mar 17 15:14:35 - validator.peer(152): Inconsistent hash:
Mar 17 15:14:35 - validator.peer(152):   local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
Mar 17 15:14:35 - validator.peer(152):   block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq

1 risposta

voti

cryptodad · Accepted Answer · 2019-03-17

5

2019-03-17

Sono riuscito a risolvereilproblema da solo.Ilmionodo aveva rifiutato unblocco apparentemente valido.L'ho scopertoelencandoi blocchi rifiutati delnodo:

 tezos-admin-client list rejected blocks

Output:
Hash: BLqhrPaH6WQtVYZssbonME7DPiQLTvZyidkYa8dvAxxoeTsnVKD
Level: 356181
Error:
Inconsistent hash:
  local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
  block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq

Quindiilnodo ha rifiutatoilblocco a causa dei diversi hash delleintestazionie non è statoin grado di recuperare,perchéprobabilmente ha rifiutato unblocco valido.

Ho risolto questoproblema deselezionandoilblocco:

 tezos-admin-client unmark invalid BLqhrPaH6WQtVYZssbonME7DPiQLTvZyidkYa8dvAxxoeTsnVKD

Output: 
Block BLqhrPaH6WQtVYZssbonME7DPiQLTvZyidkYa8dvAxxoeTsnVKD no longer marked invalid.

Non ho ancoraidea delperché sia successo.

I was able to solve the issue myself. My node had rejected a seemingly valid block. I found this out by listing the rejected blocks of the node:

tezos-admin-client list rejected blocks

Output:
Hash: BLqhrPaH6WQtVYZssbonME7DPiQLTvZyidkYa8dvAxxoeTsnVKD
Level: 356181
Error:
Inconsistent hash:
  local: CoWYi7Nmm91pS8ZNXscNTt6uBpNdaWtpantEc3HcV3XASYEVriNS
  block_header: CoVHuYH6TpDbJjXFqRsZXichbxdnvqWrDSaGpjVAsJRknAMk8Lkq

So the node rejected the block due to the different hashes of the headers and was not able to catch up, because it likely rejected a valid block.

I solved this issue by unmarking the block:

tezos-admin-client unmark invalid BLqhrPaH6WQtVYZssbonME7DPiQLTvZyidkYa8dvAxxoeTsnVKD

Output: 
Block BLqhrPaH6WQtVYZssbonME7DPiQLTvZyidkYa8dvAxxoeTsnVKD no longer marked invalid.

I still have no idea why this happened.

Benfatto dopo averlo scopertoe grazieper avercelofatto sapere!Potresti volerpresentare unticket sutezosgitlabper ulteriore aiuto sul *perché * è successo: https://gitlab.com/tezos/tezos/issuespuoi sempretornare a questa domanda.

Well done on findint this out and thanks for letting us know! You may want to file a ticket on tezos gitlab for further help on *why* this happened: https://gitlab.com/tezos/tezos/issues you can always point back to this question.
- 1
- 2019-03-17
- Ezy
Hmmm ... Hoprovato questoma ho ottenuto zeroblocchinon validi.

Hmmm... I tried this but I got zero invalid blocks.
- 0
- 2019-11-14
- Luis
Quindinon è lo stessoproblema descritto sopra.

Then it's not the same issue as described above.
- 0
- 2019-11-15
- cryptodad