cannot connect to peers on gaia-9001

[pbostrom]

Summary of Bug

I cannot connect to any peers on gaia-9001. Running on AWS EC2.

# /opt/gopath/bin/gaiacli status
{"node_info":{"protocol_version":{"p2p":"4","block":"7","app":"0"},"id":"421703a7ba396ef9b40d977b20a34d57e6d9bcf5","listen_addr":"tcp://0.0.0.0:26656","network":"gaia-9001","version":"0.26.0","channels":"4020212223303800","moniker":"","other":{"tx_index":"on","rpc_address":"tcp://0.0.0.0:26657"}},"sync_info":{"latest_block_hash":"","latest_app_hash":"","latest_block_height":"0","latest_block_time":"1970-01-01T00:00:00Z","catching_up":true},"validator_info":{"address":"5A8A8281C3CB5BD981BF6DEF4D25DDE477754E51","pub_key":{"type":"tendermint/PubKeyEd25519","value":"P4nK6Bn+fFFizWOGflrh6xM9TT9EkJm4JcIoELPH7Ck="},"voting_power":"0"}}
root@ip-10-255-225-12:/home/ubuntu# /opt/gopath/bin/gaiad version
0.26.1-rc1-0-gbb54a0d

config.toml is default except for:

#external_address = "tcp://34.229.197.75:26656"
external_address = ""

persistent_peers = "6a04069a2736f096404df2bbc31d7c2807c080c0@gaia-validator1.interblock.io:26656,aa3464017cd5abd9ff0204f2e161d66f9442db29@gaia-validator2.interblock.io:26656,f7290d305237b3fef01a59a4919aa6b399234983@gaia-validator3.interblock.io:26656,a966b0806aca7e62d5c43d8bd09425aecdcf44f2@gaia-validator4.interblock.io:26656,8a2f84e18c48ed7749d717a245850d92f3361086@144.217.247.181:26656,8461dbe5e820403ee5b029f39a2c42b11057ee0d@51.38.113.60:26656"

seeds = "7c8b8fd03577cd4817f5be1f03d506f879df98d8@gaia-seed1.interblock.io:26656,a28737ff02391a6e00a1d3b79befd57e68e8264c@gaia-seed2.interblock.io:26656,987ffd26640cd03d08ed7e53b24dfaa7956e612d@gaia-seed3.interblock.io:26656,09dafbaa69899c220d2651f51205eefe9f78737a@gaia-seed4.interblock.io:26656"

I have tried setting external_address to my public IP, no difference. I see these errors trying to connect to peers:

Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: I[10116-11-10|04:26:01.388] Will dial address                            module=p2p addr=8461dbe5e820403ee5b029f39a2c42b11057ee0d@51.38.113.60:26656
Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: I[10116-11-10|04:26:01.389] Dialing peer                                 module=p2p address=8461dbe5e820403ee5b029f39a2c42b11057ee0d@51.38.113.60:26656
Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: I[10116-11-10|04:26:01.656] Starting Peer                                module=p2p peer=0xa47a50 impl="Peer{MConn{51.38.113.60:26656} 8461dbe5e820403ee5b029f39a2c42b11057ee0d out}"
Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: I[10116-11-10|04:26:01.656] Starting MConnection                         module=p2p peer=0xa47a50 impl=MConn{51.38.113.60:26656}
Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: I[10116-11-10|04:26:01.656] Added peer                                   module=p2p peer="Peer{MConn{51.38.113.60:26656} 8461dbe5e820403ee5b029f39a2c42b11057ee0d out}"
Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: E[10116-11-10|04:26:01.656] Connection failed @ recvRoutine (reading byte) module=p2p peer=0xa47a50 conn=MConn{51.38.113.60:26656} err=EOF
Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: I[10116-11-10|04:26:01.656] Stopping MConnection                         module=p2p peer=0xa47a50 impl=MConn{51.38.113.60:26656}
Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: E[10116-11-10|04:26:01.656] Stopping peer for error                      module=p2p peer="Peer{MConn{51.38.113.60:26656} 8461dbe5e820403ee5b029f39a2c42b11057ee0d out}" err=EOF
Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: I[10116-11-10|04:26:01.656] Stopping Peer                                module=p2p peer=0xa47a50 impl="Peer{MConn{51.38.113.60:26656} 8461dbe5e820403ee5b029f39a2c42b11057ee0d out}"
Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: I[10116-11-10|04:26:01.657] Stopping gossipDataRoutine for peer          module=consensus peer="Peer{MConn{51.38.113.60:26656} 8461dbe5e820403ee5b029f39a2c42b11057ee0d out}"
Nov 10 04:26:01 ip-10-255-225-12 gaiad[10881]: I[10116-11-10|04:26:01.657] Stopping gossipVotesRoutine for peer         module=consensus peer="Peer{MConn{51.38.113.60:26656} 8461dbe5e820403ee5b029f39a2c42b11057ee0d out}"
Nov 10 04:26:03 ip-10-255-225-12 gaiad[10881]: I[10116-11-10|04:26:03.656] Stopping queryMaj23Routine for peer          module=consensus peer="Peer{MConn{51.38.113.60:26656} 8461dbe5e820403ee5b029f39a2c42b11057ee0d out}"

Steps to Reproduce

gaiad init
Download genesis.json for gaia-9001
Edit config.toml as above
gaiad start

gaiad unsafe-reset-all also has no effect.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[awrelll]

Using systemd ?

[pbostrom]

@awrelll I tried using systemd and running from shell.

[pbostrom]

Ok, I've figured out the problem:
gaiad init <--- won't connect to peers, never syncs
gaiad init --moniker mymoniker <--- works fine

So either a bug or --moniker <name> should be a required flag for gaiad

[alexanderbez]

init just generates configuration and validator files, it doesn't start any binaries. Are you stating that without the moniker, the chain never syncs?

In any case, --name should be required imho. I think we can easily and quickly resolve that.

[pbostrom]

@alexanderbez yes, if I init without a moniker, when I start gaiad, it drops all connections to peers, and never syncs. I think requiring --moniker would be a good resolution.

My motivation for dropping --moniker is that I'm configuring sentry nodes and was planning to treat them as somewhat ephemeral, and I wasn't intending to come up with a naming scheme. But if it's indeed required, then gaiad init should enforce it.