Following the scripts in validator-dynamic I run the docker network with 5 validators.
docker/validator-dynamic/run.sh and my output looks more or less like this:
WARN 2020-04-02 18:07:14 consensus/src/chained_bft/event_processor.rs:513 Round 1 timed out: already executed and voted at this round, expected round proposer was ["5707b4b6", "15977bf9"], broadcasting the vote to all replicas WARN 2020-04-02 18:07:14 network/src/peer_manager/mod.rs:475 Peer 15977bf9 is not connected WARN 2020-04-02 18:07:14 network/src/peer_manager/mod.rs:475 Peer a8fab1c1 is not connected INFO 2020-04-02 18:07:15 network/src/peer_manager/mod.rs:366 Inbound connection with peer a8fab1c1 established INFO 2020-04-02 18:07:15 network/src/protocols/direct_send/mod.rs:145 Starting direct send actor for peer: a8fab1c1 INFO 2020-04-02 18:07:15 network/src/protocols/direct_send/mod.rs:200 DirectSend inbound substream with peer a8fab1c1 for protocol ConsensusDirectSend opened INFO 2020-04-02 18:07:15 network/src/protocols/direct_send/mod.rs:200 DirectSend inbound substream with peer 140582ca for protocol DiscoveryDirectSend opened INFO 2020-04-02 18:07:15 network/src/protocols/discovery/mod.rs:336 Received updated note for peer: 140582ca from peer: 140582ca INFO 2020-04-02 18:07:15 network/src/peer_manager/mod.rs:366 Inbound connection with peer 15977bf9 established INFO 2020-04-02 18:07:15 network/src/protocols/direct_send/mod.rs:145 Starting direct send actor for peer: 15977bf9 INFO 2020-04-02 18:07:15 network/src/protocols/direct_send/mod.rs:200 DirectSend inbound substream with peer 15977bf9 for protocol ConsensusDirectSend opened INFO 2020-04-02 18:07:16 network/src/protocols/direct_send/mod.rs:200 DirectSend inbound substream with peer a8fab1c1 for protocol DiscoveryDirectSend opened INFO 2020-04-02 18:07:16 network/src/protocols/discovery/mod.rs:336 Received updated note for peer: a8fab1c1 from peer: a8fab1c1 WARN 2020-04-02 18:07:16 consensus/src/chained_bft/liveness/pacemaker.rs:190 Local timeout for round 2
Is this supposed to be correct? When I try to attach the cli to the validator (I publish the port 6180 in the docker run that was missing) with cargo run --bin cli – -u http://localhost:6180 I get:
ERROR 2020-04-02 21:06:15 common/crash-handler/src/lib.rs:38 details = ‘’’
panicked at 'Not able to connect to validator at http://localhost:6180. Error: Failed to get state proof with error: error sending request for url (http://localhost:6180/): operation timed out
and from the docker network side:
WARN 2020-04-02 21:06:05 network/src/peer_manager/mod.rs:924 Connection from /ip4/172.18.0.1/tcp/41076 failed to upgrade unexpected end of file
WARN 2020-04-02 21:06:10 network/src/peer_manager/mod.rs:924 Connection from /ip4/172.18.0.1/tcp/41080 failed to upgrade unexpected end of file
WARN 2020-04-02 21:06:15 network/src/peer_manager/mod.rs:924 Connection from /ip4/172.18.0.1/tcp/41084 failed to upgrade unexpected end of file