Unable to connect: status is continually "Attempting connection"


#1

I’m working through the Getting Started document but I’m unable to do anything that requires a connection to the Sovrin networks.

ALICE@test> connect test
Already connected to test

Usage:
    connect <test|live>


ALICE@test> accept invitation from Faber
Expanding Faber to "Faber College"
Invitation not yet verified.
Link not yet synchronized.
Invitation acceptance aborted.
Cannot sync because not connected. Please connect first.
ALICE@test> ping faber
Expanding faber to "Faber College"
Please sync first to get target endpoint
ALICE@test> status
Attempting connection to test Sovrin network

I get the same results when connecting to “live”. The status never changes.

I created this new installation today. Note: after the basic installation my “pool_transactions_sandbox” file was empty, so I had to manually add the contents from GitHub.

Any suggestions?
Trent

PS: Here’s the startup info:

$ sovrin
Loading module /usr/local/lib/python3.5/dist-packages/config/config-crypto-example1.py
Module loaded.

Sovrin-CLI (c) 2017 Evernym, Inc.
Node registry loaded.
    EvernymV1: 52.33.22.91:9721
    EvernymV2: 52.38.24.189:9723
    WSECU: 40.121.149.41:9725
    BIG: 52.160.103.164:9727
    RespectNetwork: 54.173.9.185:9729
    FCU: 69.144.146.171:9733
    BYU: 54.193.6.155:9744
    BULLDOG: 52.56.74.57:9746
Type 'help' for more information.
Running Sovrin 0.3.17

sovrin> connect test

Saved keyring "Default" restored (/home/ubuntu/.sovrin/keyrings/test/default.wallet)
Active keyring set to "Default"
Client sovrinVK2dop initialized with the following node registry:
    EvernymV1C      listens at 52.33.22.91    on port 9722
    EvernymV2C      listens at 52.38.24.189   on port 9724
    WSECUC          listens at 40.121.149.41  on port 9726
    BIGC            listens at 52.160.103.164 on port 9728
    RespectNetworkC listens at 54.173.9.185   on port 9730
    FCUC            listens at 69.144.146.171 on port 9734
    BYUC            listens at 54.193.6.155   on port 9745
    BULLDOGC        listens at 52.56.74.57    on port 9747
Active client set to sovrinVK2dop
6NHkS7aXywwgnGakuAGxi3vg6m1KAr7VBJZVEPkRfpQZ listening for other nodes at 0.0.0.0:6006
6NHkS7aXywwgnGakuAGxi3vg6m1KAr7VBJZVEPkRfpQZ looking for BULLDOGC at 52.56.74.57:9747
6NHkS7aXywwgnGakuAGxi3vg6m1KAr7VBJZVEPkRfpQZ looking for BYUC at 54.193.6.155:9745
6NHkS7aXywwgnGakuAGxi3vg6m1KAr7VBJZVEPkRfpQZ looking for EvernymV2C at 52.38.24.189:9724
6NHkS7aXywwgnGakuAGxi3vg6m1KAr7VBJZVEPkRfpQZ looking for BIGC at 52.160.103.164:9728
6NHkS7aXywwgnGakuAGxi3vg6m1KAr7VBJZVEPkRfpQZ looking for RespectNetworkC at 54.173.9.185:9730
6NHkS7aXywwgnGakuAGxi3vg6m1KAr7VBJZVEPkRfpQZ looking for WSECUC at 40.121.149.41:9726
6NHkS7aXywwgnGakuAGxi3vg6m1KAr7VBJZVEPkRfpQZ looking for EvernymV1C at 52.33.22.91:9722
6NHkS7aXywwgnGakuAGxi3vg6m1KAr7VBJZVEPkRfpQZ looking for FCUC at 69.144.146.171:9734
Connecting to test...
sovrin@test>

#2

Hi, @trentlarson. You don’t mention which way you set up your test environment. Did you install stuff from .deb files, or did you use pip, or did you install from source, or use vagrant or docker or an AMI on AWS? Also, are you using the master or the stable branch of the code?

I see from your genesis transactions that you may be talking to networks that have been in flux over the past couple days (we have been restarting some nodes and reconnecting them as we wind down the logistical work of the launch of the provisional network in the near future…). None of what we’ve done should make your workflow impossible or destined to fail, AFAIK, but maybe the vagrant path would be the easiest way to take that variable out of the equation. (The vagrant setup powers up 4 virtual machines in your local env so you can use them without depending on anybody else.)

The vagrant setup is documented in the Getting Started Guide that appears in the master branch of the code at https://github.com/sovrin-foundation/sovrin-client/blob/master/getting-started.md. See https://github.com/evernym/sovrin-environments/blob/master/vagrant/training/vb-multi-vm/TestSovrinClusterSetup.md


#3

Thanks for the quick response!

To set up the instance, I created an Ubuntu 16.04 instance in AWS and did the following in it:

sudo apt-get update
sudo apt install python3-pip python3.5-dev unzip make libsodium18

wget https://raw.githubusercontent.com/evernym/anoncreds/master/setup-charm.sh
chmod +x setup-charm.sh
./setup-charm.sh

sudo ldconfig

pip3 install -U --no-cache-dir sovrin-client

sudo -H pip3 install virtualenvwrapper

echo '' >> ~/.bashrc
echo '# Python virtual environment wrapper' >> ~/.bashrc
echo 'export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python3' >> ~/.bashrc
echo 'export WORKON_HOME=$HOME/.virtualenvs' >> ~/.bashrc
echo 'source /usr/local/bin/virtualenvwrapper.sh' >> ~/.bashrc
source ~/.bashrc
mkvirtualenv sovrin
workon sovrin

mkdir .sovrin
wget https://raw.githubusercontent.com/sovrin-foundation/sovrin-client/stable/data/pool_transactions_sandbox
mv pool_transactions_sandbox .sovrin/

sovrin

After that, I get the same output as I wrote previously… though I can paste the whole session if you like.

I appreciate the quick response because I’m trying to get a proof-of-concept done by tomorrow, so I’d love to show a good result.

Thanks again for any help.
Trent

PS: I also appreciate the pointer to Vagrant instructions, since I failed on that route as well (as you can see from the other issue I logged today): it may have to do with the “pubkey”, so I’ll try again.


#4

I checked with our QA folks. They confirmed that the genesis transactions for the “live” and “test” network both point to machines that are under active maintenance–thus the failure to connect is pretty likely.

For the next little while, your best bet is the vagrant solution. No dependencies, should work out of the box.


#5

Using the Vagrant instructions in TestSovrinClusterSetup.md I end up hacking the validator.sh script. Seems it attempts do execute things as user “sovrin”, but none have been created. So I added:
useradd -ms /bin/bash -u 1001 sovrin
but then it appears that execution of “init_sovrin_node” and other things cannot be found.

Is this supposed to be stable on “master”, or do I need to go to some branch?


#6

Actually the Docker version based on


seems to work much better than the Vagrant one.

I was wondering: Should the “Getting Started with Sovrin” tutorial work with the above, or do I need to setup a Faber agent on top of that somehow?


Current way to run client demo (docker?)
#7

Thank you for the info, Daniel.


#8

This is an old thread, but just in case someone stumbles across it, the correct location of the Getting Started Guide is now https://github.com/hyperledger/indy-node/blob/stable/getting-started.md