Supress error messages while using mock

[BlackDuck888]

My installation starts in a fresh Ubuntu Xenial LXC Container, i did this twice.

I started from scratch with following commands

sudo apt update
sudo apt full-upgrade
sudo apt autoremove 
sudo apt clean
sudo apt install openssh-server git curl nano

wget -q https://storage.googleapis.com/golang/getgo/installer_linux
chmod +x installer_linux 
./installer_linux 

$ Welcome to the Go installer!
$ Downloading Go version go1.11.2 to /home/ubuntu/.go
$ This may take a bit of time...
$ Downloaded!
$ Setting up GOPATH
$ GOPATH has been set up!

$ One more thing! Run `source /home/ubuntu/.bash_profile` to persist the
$ new environment variables to your current session, or open a
$ new shell prompt.

source /home/ubuntu/.bash_profile
go version
$ go version go1.11.2 linux/amd64

git clone https://github.com/storj/storj.git storj
$ Cloning into 'storj'...
$ remote: Enumerating objects: 72, done.
$ remote: Counting objects: 100% (72/72), done.
$ remote: Compressing objects: 100% (60/60), done.
$ remote: Total 7570 (delta 20), reused 40 (delta 7), pack-reused 7498
$ Receiving objects: 100% (7570/7570), 20.35 MiB | 1.86 MiB/s, done.
$ Resolving deltas: 100% (4097/4097), done.
$ Checking connectivity... done.

cd storj
go install ./cmd/captplanet
$ <snip>
$ ....
$ go: downloading github.com/pkg/errors v0.8.0
$ go: downloading github.com/eapache/queue v1.1.0
$ go: downloading github.com/prometheus/procfs v0.0.0-20180725123919-05ee40e3a273
$ go: downloading github.com/eapache/go-xerial-snappy v0.0.0-20180814174437-776d5712da21
$ go: downloading github.com/mattn/go-colorable v0.0.9
$ go: downloading github.com/golang/snappy v0.0.0-20180518054509-2e65f85255db


captplanet setup
$ <snip>
$ creating identity for storage node 98
$ creating identity for storage node 99
$ creating identity for storage node 100
$ creating identity for uplink

captplanet run

starting storage node 0 fSoUlG1bIPl8aOEP8aycdIcqwOsyzhK8-AycHIFBEAA=:127.0.0.1:7780 (kad on 

127.0.0.1:7781)
starting storage node 1 9IO9g1-gVgs9SJdLWRa-2HDmQDdQ0pEv0_AywOxkkAA=:127.0.0.1:7782 (kad on 

127.0.0.1:7783)
starting storage node 2 09sc94eCE8bBH3MrUmrfzPU-DBPgUlTDLQlfSrkC0AA=:127.0.0.1:7784 (kad on 

127.0.0.1:7785)
starting storage node 3 zbvqg7jPxjMALK30RNDukHVbSau-10l3iwawe0gG8AA=:127.0.0.1:7786 (kad on 

127.0.0.1:7787)
starting storage node 4 gYfOb0DPkSvr5hQCyVLtNnPFuTIaLsrH3_UVUlCA8AA=:127.0.0.1:7788 (kad on 

127.0.0.1:7789)
starting storage node 5 LnYsT-BySxttFu4XaRuZd3l9DydnultaRAhXXw8YgAA=:127.0.0.1:7790 (kad on 

127.0.0.1:7791)
starting storage node 6 kxIxg3512hB3XTP-CMAV1rsQX4KTH9MCYFw_D9XggAA=:127.0.0.1:7792 (kad on 

127.0.0.1:7793)
starting storage node 7 TlQDdDPH_OeoP7zmk3DN7Sjzc990r1yhzS_TIjoNQAA=:127.0.0.1:7794 (kad on 

127.0.0.1:7795)
starting storage node 9 qydT2J4g4nCYc-X3pgszV2Cgt5MmWgT82ctL6h334AA=:127.0.0.1:7798 (kad on 

127.0.0.1:7799)
starting storage node 10 VrUDNUX0q09Tbf5OgX0ZtjakcgkPTEl46odc4Ki3MAA=:127.0.0.1:7800 (kad on 

127.0.0.1:7801)
starting storage node 11 X0JJaIyrIFGvMoKZP5-cEEDiKlHZ-MWA4K6Do71cwAA=:127.0.0.1:7802 (kad on 

127.0.0.1:7803)
starting storage node 8 wXkX0DOiMU_7Xn09ofWx27pw9Z3uwh_10IEV_J3OAAA=:127.0.0.1:7796 (kad on 

127.0.0.1:7797)
starting storage node 13 lf7zKiRnj9Jgseg7FL_BXrj5aHNb2uEvGeTTE-OowAA=:127.0.0.1:7806 (kad on 

127.0.0.1:7807)
starting storage node 12 1r1EskHQPSblVMnXTGHUhMcY782suzpPKrfeHKDNgAA=:127.0.0.1:7804 (kad on 

127.0.0.1:7805)
starting storage node 14 OA51vruTQiExmM_fg_1xFg_2U4hctJD35FQEIgZTQAA=:127.0.0.1:7808 (kad on 

127.0.0.1:7809)
starting storage node 17 UKk0arzKKkQO-Wea02_TMEdPjLtpxKyPwaHXljC0sAA=:127.0.0.1:7814 (kad on 

127.0.0.1:7815)
starting storage node 20 plX4GnRezMnfkgxRVrPFtnHHl_Df9_Qs7lj5GoDTkAA=:127.0.0.1:7820 (kad on 

127.0.0.1:7821)
2018-11-14T10:15:50.939Z        ERROR   Error occurred during lookup of 09sc94eCE8bBH3MrUmrfzPU-

DBPgUlTDLQlfSrkC0AA= :: max retries exceeded for id:: foo :: error = node client error: rpc error: 

code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: 

connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:7778: connect: 

connection refused"
starting storage node 16 qAAutUfO0eNrCRrHQa2g5j-VeE3v7qKWudRvH9cUYAA=:127.0.0.1:7812 (kad on 

127.0.0.1:7813)
starting storage node 19 GoTJ88wRw9tRKukdDS0Ab_vjlIK63by6l5dnMhLaoAA=:127.0.0.1:7818 (kad on 

127.0.0.1:7819)
starting storage node 18 MMn8pQ6ZvUwTBdaVWHHSXBn-URaN80340if7sferEAA=:127.0.0.1:7816 (kad on 

127.0.0.1:7817)
2018-11-14T10:15:50.939Z        ERROR   Error occurred during lookup of X0JJaIyrIFGvMoKZP5-

cEEDiKlHZ-MWA4K6Do71cwAA= :: max retries exceeded for id:: foo :: error = node client error: rpc 

error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: 

connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:7778: connect: 

connection refused"
starting storage node 15 dVLHIghbO1o0cexGgGy7THw0JHcJUMOOf-cGgpnyIAA=:127.0.0.1:7810 (kad on 

127.0.0.1:7811)
2018-11-14T10:15:50.940Z        ERROR   Error occurred during lookup of X0JJaIyrIFGvMoKZP5-

cEEDiKlHZ-MWA4K6Do71cwAA= :: max retries exceeded for id:: X0JJaIyrIFGvMoKZP5-cEEDiKlHZ-

MWA4K6Do71cwAA= :: error = node client error: rpc error: code = Unavailable desc = all SubConns 

are in TransientFailure, latest connection error: connection error: desc = "transport: Error while 

dialing dial tcp 127.0.0.1:7803: connect: connection refused"

What can i do to get it running.

[littleskunk]

Looks good to me. Captplanet is using a mock instead of the kademlia network. For the moment please ignore the connection errors. As long as captplanet is not crashing and still running you should be able to up and download files.

[BlackDuck888]

It should be helpfull that in this way of usage such error messages will be suppressed. The captplanet ist plannend/designed for developer? They will get enough errormessages, it will be hard to differ between real and fake errors, and at the and developers will start to develope in mainnet, and this will not be helpfull for everyone.

[RichardLitt]

Great idea, @BlackDuck888! We’d love a PR for this.

Mind if I change the title of this post to reflect the feature you’ve suggested? Feel free to take it on yourself if you're keen.

[BlackDuck888]

Feel free to change it to your needs. @RichardLitt

[coyle]

This was fixed at #627

We are no longer using the mock so the messages have gone away.