Docker image can't sync to test network

[andrevtg]

When using the Docker image:

docker run --rm -ti --net=host sovrinfoundation/sovrin

root@node1:/# sovrin
Loading module /usr/local/lib/python3.5/dist-packages/config/config-crypto-example1.py
Module loaded.

Sovrin-CLI (c) 2016 Evernym, Inc.
Node registry loaded.
    BYU: 54.193.6.155:9744
    BIG: 52.160.103.164:9727
    FCU: 69.144.146.171:9733
    EvernymV2: 52.38.24.189:9723
    EvernymV1: 52.33.22.91:9721
    RespectNetwork: 54.173.9.185:9729
    WSECU: 13.93.218.255:9725
Type 'help' for more information.
sovrin> connect test
New keyring Default created
Active keyring set to "Default"
Client sovrinAzta3P 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 13.93.218.255  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
Active client set to sovrinAzta3P
sovrinAzta3P listening for other nodes at 0.0.0.0:8307
sovrinAzta3P looking for FCUC at 69.144.146.171:9734
sovrinAzta3P looking for BIGC at 52.160.103.164:9728
sovrinAzta3P looking for RespectNetworkC at 54.173.9.185:9730
sovrinAzta3P looking for EvernymV2C at 52.38.24.189:9724
sovrinAzta3P looking for WSECUC at 13.93.218.255:9726
sovrinAzta3P looking for EvernymV1C at 52.33.22.91:9722
sovrinAzta3P looking for BYUC at 54.193.6.155:9745
Connecting to test...
sovrinAzta3P now connected to RespectNetworkC
sovrinAzta3P now connected to EvernymV1C
sovrinAzta3P now connected to EvernymV2C
sovrinAzta3P now connected to BYUC
Connected to test.
sovrinAzta3P now connected to BIGC
sovrinAzta3P could not verify catchup reply CATCHUP_REP(ledgerType=0, txns={'8': {'reqId': 1478156921805694, 'txnId': 'bfa9e020f5963c12132024
d5a2067c2bd6f53b5244cf247e9e50872c9249704b', 'data': {'node_port': 9725, 'client_ip': '40.121.149.41', 'client_port': 9726, 'node_ip': '40.12
1.149.41', 'alias': 'WSECU'}, 'dest': 'AZsp46qSPGjHuNYajiMUb5XcMWCRDuk2xdEv7P5MepSN', 'identifier': 'CECeGXDi6EHuhpwz19uyjjEnsRGNXodFYqCRgdLm
LRkt', 'type': 'CHANGE_HA', 'txnTime': 1478157003369.697}}, consProof=['XmKV6S2v0aU+ShLDNYNTRqept9Wv/n6sPxUGoc0mSIA=']) since Bad Merkle proo
f: second root hash does not match. Expected hash: b'5b5c7b0062201f34f98a7505340db13494e5a425bdac28ea0041c5b8e973df71' , computed hash: b'044
4f93850f58a4a62f25a18f3ade3f4c6ca8c69a2a52a1aac305df3d86e889b'
sovrinAzta3P looking for FCUC at 69.144.146.171:9734
sovrinAzta3P looking for WSECUC at 13.93.218.255:9726
sovrinAzta3P looking for FCUC at 69.144.146.171:9734
(...)

The "Getting Started" instructions fail because sync never occurs.

[azheregelya]

Hello @andrevtg. Thank you for your participation
I just wanted to say that we are working on this issue.
I've reproduced it and had a chat with @lovesh
We will write updates here.

[azheregelya]

@andrevtg
UPD: Glad to inform, that cluster is up.
It was updated to sovrin 0.1.139 and plenum 0.1.158, so update your sovrin setup as well.
Don't worry about BIGC node. It's down currently and doesn't affect on consensus.
You can run Faber test from "Sovrin Getting Started" to check it.

[PhillMoran]

Seems like there are other issues with the Docker Image - cannot connect to test.
Constantly looking for endpoints, but not connecting to test....

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.

Usage:
connect <test|live>

[dhh1128]

@PhillBO I was able to replicate your issue today. It's a problem with the docker image, it is caused by few of our validator nodes in the test network crashed and some issues with our communication protocol. We have identified part of the problem today (one of the workflows that dup'ed the problem started working, but another is still blocked). We will report back on further progress within 24 hours.

[PhillMoran]

Great stuff! Looking forward to really getting to task with your platform. Thanks!

[PhillMoran]

picking this up again - some success... another fail...
looks like connecting to test now works...
ALICE@test> status
Connected to test Sovrin network

however, next step - fails
ALICE@test> accept invitation from faber
Expanding faber to "Faber College"
Invitation not yet verified.
Attempting to sync...
Synchronizing...
Link Faber College synced
Pinging target endpoint: ('127.0.0.1', 5555)
[Not Yet Implemented]

[dhh1128]

@PhillBO The "Not Yet Implemented" message tells me that the code that ran was old. We took that message out a while ago. I'm scratching my head, wondering what went wrong.

I wonder if you could update your code (pip install sovrin -U) and see if the outcome changes.

[PhillMoran]

Updated - results below...
I am running the latest docker on OSX, no firewalls...

ALICE@test> accept invitation from faber
Expanding faber to "Faber College"
Invitation not yet verified.
Attempting to sync...

Synchronizing...
Link Faber College synced

Pinging target endpoint: ('127.0.0.1', 5555)
Ping sent.
No response received within specified time (8000 mills). Retry the command and see if that works.

ALICE@test>

[andrevtg]

Please try running the container with "--net=host". Em sex, 6 de jan de 2017 às 14:36, phillbo <[email protected]> escreveu:

…

Updated - results below... I am running the latest docker on OSX, no firewalls... ***@***.***> accept invitation from faber Expanding faber to "Faber College" Invitation not yet verified. Attempting to sync... Synchronizing... Link Faber College synced Pinging target endpoint: ('127.0.0.1', 5555) Ping sent. No response received within specified time (8000 mills). Retry the command and see if that works. ***@***.***> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <sovrin-foundation/sovrin#26 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJ3LO0aG5mgqfF8TBNVciTd_k_iZsF7xks5rPm13gaJpZM4K6fr3> .

[PhillMoran]

I looked at some notes on Kinematic and Docker for OS X, looks like there are some minor issues with proxy… to remove those, I’ll set up a Ubuntu server this weekend and start form scratch! I’ll let you know when I get success… thanks!

…

On Jan 6, 2017, at 8:38 AM, André Fernandes ***@***.***> wrote: Please try running the container with "--net=host". Em sex, 6 de jan de 2017 às 14:36, phillbo ***@***.***> escreveu: > Updated - results below... > > > I am running the latest docker on OSX, no firewalls... > > > ***@***.***> accept invitation from faber > > > Expanding faber to "Faber College" > > > Invitation not yet verified. > > > Attempting to sync... > > > Synchronizing... > > > Link Faber College synced > > > Pinging target endpoint: ('127.0.0.1', 5555) > > > > Ping sent. > > > No response received within specified time (8000 mills). Retry the command > and see if that works. > > > ***@***.***> > > > > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <sovrin-foundation/sovrin#26 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AJ3LO0aG5mgqfF8TBNVciTd_k_iZsF7xks5rPm13gaJpZM4K6fr3> > . > > > > > > > > > > > > > > > > > > > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <sovrin-foundation/sovrin#26 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACSRUTo1_vR3HWcu0-ZYIA963QBM3YYIks5rPm3ogaJpZM4K6fr3>.