cli
cli copied to clipboard
Network: Can't launch `0.46` spn with several validators
Describe the bug
Tested launching spn
on 0.46
on Gitpod
It seems the chain with two validators can't be started because of peer connection issue
8:00AM INF service start book=/home/gitpod/spn/1/config/addrbook.json impl=AddrBook module=p2p msg={}
8:00AM ERR Can't add peer's address to addrbook err="Cannot add non-routable address [email protected]:22001" module=p2p
8:00AM INF Saving AddrBook to file book=/home/gitpod/spn/1/config/addrbook.json module=p2p size=0
8:00AM INF Ensure peers module=pex numDialing=0 numInPeers=0 numOutPeers=0 numToDial=10
8:00AM INF No addresses to dial. Falling back to seeds module=pex
8:00AM INF serve module=api-server msg={}
8:00AM INF Dialing peer address={"id":"151227214df2276ca2cdb71e19a859fb26da46b8","ip":"127.0.0.1","port":22001} module=p2p
8:00AM ERR Error dialing peer err="dial tcp 127.0.0.1:22001: connect: connection refused" module=p2p
8:00AM INF Reconnecting to peer addr={"id":"151227214df2276ca2cdb71e19a859fb26da46b8","ip":"127.0.0.1","port":22001} module=p2p
8:00AM INF Dialing peer address={"id":"151227214df2276ca2cdb71e19a859fb26da46b8","ip":"127.0.0.1","port":22001} module=p2p
8:00AM INF Error reconnecting to peer. Trying again addr={"id":"151227214df2276ca2cdb71e19a859fb26da46b8","ip":"127.0.0.1","port":22001} err="dial tcp 127.0.0.1:22001: connect: connection refused" module=p2p tries=0
8:00AM INF Dialing peer address={"id":"151227214df2276ca2cdb71e19a859fb26da46b8","ip":"127.0.0.1","port":22001} module=p2p
8:00AM INF Error reconnecting to peer. Trying again addr={"id":"151227214df2276ca2cdb71e19a859fb26da46b8","ip":"127.0.0.1","port":22001} err="dial tcp 127.0.0.1:22001: connect: connection refused" module=p2p tries=1
What version are you using?
feat/sdk-ibc-upgrade
cli
develop
spn
Not happening for other 0.46
scaffolded chain. Maybe an issue with app package
SPN doesn't have Gitpod proxy enabled for now
@fadeev The bug still exists for you?
I'm currently looking into it
@fadeev The bug still exists for you?
The one described in the docs PR, yes.
The only thing I've noticed so far is that when you ignite n chain init
it creates a gentx.json
, but when you ignite n chain prepare
, the same file is called gentx1.json
.
/workspace/go/bin/ignite network tool proxy-tunnel /home/gitpod/spn/27/spn.yml & exampled start --home /home/gitpod/spn/27
it seems the proxy config file is not created:
cat /home/gitpod/spn/27/spn.yml
cat: /home/gitpod/spn/27/spn.yml: No such file or directory
However, running ignite network tool proxy-tunnel /home/gitpod/spn/27/spn.yml
doesn't seem to create an error
@tbruyelle did you work on network tool proxy-tunnel
?
Is it normal the command can run without a config but immediately return?