Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-1106

Live network node does not sync following BLS upgrade

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Complete
    • Priority: Highest
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      1.2.50

    • Epic Link:
    • Sprint:
      Sprint 18.03 Stability, DKMS, Sprint 18.04, Sprint 18.05, 18.06

      Description

      The steward made a mistake and did "init_bls_keys" as root instead of as the indy user. This resulted in a misconfiguration, with no bls data in the /var/lib/indy/live/keys/<ALIAS>/bls_keys folder. He then put the bls key data for that node into the ledger.

      His pool ledger is now out of sync, lacking the last 2 transactions, including his own. I later got online with him to debug this. I discovered the error, and had him re-run the init_bls_keys as the indy user. The correct values are now in the /var/lib/indy/live/keys/<ALIAS>/bls_keys folder, matching what is on the ledger. However, his node will still not sync. I do not see responses to his pings in his logs, although in the ev1 logs it looks like our node is responding.

      Logs are attached.

        Attachments

        1. DustStorm.log
          224 kB
        2. ev1_ledger.txt
          11 kB
        3. ev1.log.tgz
          468 kB

          Issue Links

            Activity

              People

              Assignee:
              mgbailey Mike Bailey
              Reporter:
              mgbailey Mike Bailey
              Watchers:
              Alexander Shcherbakov, Dmitry Surnin, Mike Bailey
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: