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

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

    XMLWordPrintable

Details

    • Bug
    • Status: Complete
    • High
    • Resolution: Done
    • None
    • 1.6.79
    • None
    • Unset
    • 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

        1. xsvalidatorec2irl_pool_ledger.txt
          38 kB
          Mike Bailey
        2. xsvalidatorec2irl_validator_info.json
          12 kB
          Mike Bailey

        Activity

          People

            mgbailey Mike Bailey
            mgbailey Mike Bailey
            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: