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

Node that is not on network is shown as 'unreachable'

    Details

    • Type: Bug
    • Status: Complete
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.6.79
    • Component/s: None
    • Labels:
    • Documentation Impact:
      Unset
    • Sprint:
      Ev 18.23

      Description

      This behavior has manifest on two new validators that were onboarded to TestNet this week, but not on the other validators on that network. TestNet is running indy-node=1.6.78.

      valNode01 is a node that was once on the TestNet, but it has been removed with a ledger entry with services=[] written to the ledger. The issue is that in spite of this, this node is shown as if it is an active node that is unreachable in validator-info. In the logs, you can see that the new validators are attempting to contact it as well. This occurs on these 2 new validators, but not on the other  ones in the pool. At least for these 2 validators, this is a drag on consensus, and could also influence client behavior as well.

      The pool ledgers are in sync on all nodes.

      validator-info output,  the pool ledger, and logs from one of the new nodes are attached.

        Attachments

          Activity

            People

            • Assignee:
              mgbailey Mike Bailey
              Reporter:
              mgbailey Mike Bailey
              Watchers:
              Alexander Shcherbakov, Artem Obruchnikov, Dmitry Surnin, Kelly Wilson, Mike Bailey, Richard Esplin
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: