Error: “inconsistent hash”. Workers crash and node is unable to connect to others

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












4















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









share|improve this question




























    4















    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









    share|improve this question


























      4












      4








      4


      1






      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









      share|improve this question
















      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






      node tezos-client error






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 17 at 16:07







      Marc.b

















      asked Mar 17 at 15:25









      Marc.bMarc.b

      532117




      532117




















          1 Answer
          1






          active

          oldest

          votes


















          5














          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.






          share|improve this answer


















          • 1





            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: gitlab.com/tezos/tezos/issues you can always point back to this question.

            – Ezy
            Mar 17 at 17:52












          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "698"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          noCode: true, onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f800%2ferror-inconsistent-hash-workers-crash-and-node-is-unable-to-connect-to-other%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          5














          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.






          share|improve this answer


















          • 1





            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: gitlab.com/tezos/tezos/issues you can always point back to this question.

            – Ezy
            Mar 17 at 17:52
















          5














          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.






          share|improve this answer


















          • 1





            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: gitlab.com/tezos/tezos/issues you can always point back to this question.

            – Ezy
            Mar 17 at 17:52














          5












          5








          5







          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.






          share|improve this answer













          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.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 17 at 15:59









          Marc.bMarc.b

          532117




          532117







          • 1





            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: gitlab.com/tezos/tezos/issues you can always point back to this question.

            – Ezy
            Mar 17 at 17:52













          • 1





            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: gitlab.com/tezos/tezos/issues you can always point back to this question.

            – Ezy
            Mar 17 at 17:52








          1




          1





          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: gitlab.com/tezos/tezos/issues you can always point back to this question.

          – Ezy
          Mar 17 at 17:52






          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: gitlab.com/tezos/tezos/issues you can always point back to this question.

          – Ezy
          Mar 17 at 17:52


















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Tezos Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftezos.stackexchange.com%2fquestions%2f800%2ferror-inconsistent-hash-workers-crash-and-node-is-unable-to-connect-to-other%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown






          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay