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

Unable to send transactions to Live Sovrin

    XMLWordPrintable

Details

    • Bug
    • Status: Complete
    • Highest
    • Resolution: Done
    • None
    • None
    • None
    • None
    • 1.1.43 upgraded to 1.2.50

    • Sprint 18.02 Stability

    Description

      Following the upgrade to to 1.2.50, the live Sovrin network is no longer processing transactions.  In particular, we are not able to do "send NODE" to configure the BLS keys.

      For example, shortly before Wed Jan 24 21:18, I sent the following transaction: 

      indy@live> send NODE dest=GWgp6huggos5HrzHVDy5xeBkYHxPvrRZzjPNAyJAqpjA data={'alias':'ev1','blskey': '2zg4ufG8iyn5BQfh1YsutZqEB4QdZt8NUvef9CX7VrqCKHsfxY2muPY3LSGbBshqB6sfvXa7zXVPFUjM1ZcZmc2RFpSKsRNQC1shGA6yLhtkG5UUkNCRfXMd2UsuLu8x1pi7fHQaD
      ioPQ8WxUf4YiJT8BuPx6RyfYRtyvuvJxr2UwBL'}
      Sending node request for node DID GWgp6huggos5HrzHVDy5xeBkYHxPvrRZzjPNAyJAqpjA by J4N1K1SEB8uY2muwmecY5q (request id: 1516830370402348)
      indy@live>
      

      No response was received at the cli.

      It appears that there are enough connected nodes for consensus:

      mikebailey@sao-sov-p001:~$ sudo validator-info -v
      [sudo] password for mikebailey:
      Validator ev1 is running
      Current time: Wednesday, January 24, 2018 9:15:39 PM
      Validator DID: GWgp6huggos5HrzHVDy5xeBkYHxPvrRZzjPNAyJAqpjA
      Verification Key: 46HnJNoJCRdFasFSBakSyqSgNGE93STk7wZiddJnsCfLgMKWjhWEJNc
      Node Port: 9701/tcp on 0.0.0.0/0
      Client Port: 9702/tcp on 0.0.0.0/0
      Metrics:
      Uptime: 8 hours, 44 minutes, 12 seconds
      Total Config Transactions: 114
      Total Ledger Transactions: 42
      Total Pool Transactions: 15
      Read Transactions/Seconds: 0.00
      Write Transactions/Seconds: 0.00
      Reachable Hosts: 12/14
      BIGAWSUSEAST1-001
      DustStorm
      OASFCU
      ServerVS
      danube
      digitalbazaar
      esatus_AG
      ev1
      prosovitor
      royal_sovrin
      thoth
      zaValidator
      Unreachable Hosts: 2/14
      icenode
      iRespond
      Software Versions:
      indy-node: 1.2.50
      sovrin: 1.1.6

      Looking at the logs they are rolling over very rapidly.  The ten logs retained on ev1 only go back about 3 hours.  They are attached.

      Also, ev1 is the first node in the genesis file, so I would expect it to be the primary.  This is not the case, and in fact the logs show that the primary has changed several times in the last few hours.

       

      Attachments

        1. BIG_Node.tar
          2.22 MB
        2. BIGAWSUSEAST1-001_ledgers.tgz
          11 kB
        3. danube_ledgers_with_config.tgz
          12 kB
        4. esatus_AG_ledgers.tgz
          11 kB
        5. esatus_config_ledger
          34 kB
        6. ev1_ledgers_with_config.tgz
          12 kB
        7. ev1_logs_1.tgz
          8.81 MB
        8. ev1_logs_2.tgz
          8.84 MB
        9. ev1_logs_3.tgz
          9.76 MB
        10. ev1_logs_4.tgz
          7.03 MB
        11. OASFCU_config_ledger
          34 kB
        12. OASFCU_ledgers.tgz
          11 kB
        13. prosovitor_ledgers_with_config.tgz
          11 kB
        14. royal_sovrin_ledgers_with_config.tgz
          12 kB
        15. ServerVS_ledgers_with_config.tgz
          12 kB
        16. thoth_ledgers.tgz
          11 kB
        17. zaValidator_ledgers_with_config.tgz
          12 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mgbailey Mike Bailey
              Alexander Shcherbakov, Mike Bailey, Nikita Spivachuk, Olga Zheregelya, Sean Bohan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: