After successful setup and blockchain sync (producer and relay nodes), I faced a problem with no inbound connections to relay node (to be more precise, one connection from the producer node). And zero processed transactions and empty mempool.
Also, I correctly installed topologyUpdater as a service with CUSTOM_PEERS param - all works as well, but zero tx processed…
Any help with this? Thanks.
How many times did u ran topology updater?
The topologyupdater shell script must be executed on the relay node as a cronjob exactly every 60 minutes. After 4 consecutive requests (3 hours) the node is considered a new relay node in listed in the topology file. If the node is turned off, it’s automatically delisted after 3 hours.
Yes, about a couple of hours ago, let’s wait. Thank you for your prompt response.
In the topologyupdater file you should see a message… “glade you are staying with us (something like that) …” then your node will be considered online; I guess now it’s showing “nice to met you…”
{ "resultcode": "504", "datetime":"2020-12-06 19:59:11", "clientIp": "178.128.178.48", "iptype": 4, "msg": "one request per hour please" }
Looks like my relay is registered.
178.128.178.48:6000 port is open, but no inbound connections.
I’m using clean Ubuntu 20 install on DigitalOcean droplets.
And yor firewall setup?
sudo ufw status
Status: active
To Action From
-- ------ ----
6000 ALLOW Anywhere
6000/tcp ALLOW Anywhere
6000 (v6) ALLOW Anywhere (v6)
6000/tcp (v6) ALLOW Anywhere (v6)
Cover your user… someone can use to hack… for both pictures…
Try also to open port 3001 on relay and restart your Relay if needed
What is your pool ticker?
I’m trying open 3001 port now… My ticker is RAY
Port 3001 is opened but still no luck
Wait a moment I just saw… in your first gliveview output on IN you have only 1 peer and I guess is your BP right? Something is blocking your incoming connections
Yes, this is connection from BP. I try to google, but really no issues like mine.
┌───────────────────────────────────────┬──────────────────────┐
│ Uptime: 07:30:00 │ Guild LiveView v1.13 │
│---------------------------------------└──────────────────────┤
│ Epoch 233 [99.0%] (node) │
│ 01:09:36 until epoch boundary (chain) │
│ ▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▌▖ │
│ │
│ Block : 5044062 Tip (ref) : 15720624 │
│ Slot : 427804 Tip (node) : 15720604 │
│ Density : 4.890 Tip (diff) : 20 :) │
│--------------------------------------------------------------│
│ Processed TX : 1 Out / In │
│ Mempool TX/Bytes : 0 / 0 Peers : 1 1 │
├──────────────────────────────────────────────────────────────┤
│ KES current/remaining : 121 / 62 │
│ KES expiration date : 2021-03-09 09:44:51 Z │
│--------------------------------------------------------------│
│ BLOCKS Leader | Adopted | Invalid │
│Since node start (EKG metrics) 0 | 0 | 0 │
└──────────────────────────────────────────────────────────────┘
Your issue is in your Relay side
Something is blocking your incoming connections; check in logs in topologyupdater log … how many times the topology script ran…nevermind I see uprime 7hours… I guess more than 4
Let me check on my Relays
Yes, I almost 7 hours try to figured it out 
Thank you for your help, it is inspiring.
we will fix it 
look my relays show more IN peers:
I think I will try to add additional relay, and build node from the scratch.
I will write results if you are interested.
wait…can you show me the config of topologyupdater script?
nano topologyupdater.sh (cover your BP IP)
mine is looking like that:
Yes, I changed just CUSTOM_PEERS in this file.
CNODE_HOSTNAME="CHANGE ME" # (Optional) Must resolve to the IP you are requesting from
CNODE_LOG_DIR="${CNODE_HOME}/logs" # Folder where your logs will be sent to (must pre-exist)
CNODE_VALENCY=1 # (Optional) for multi-IP hostnames
CNODE_TOPOLOGY="${CNODE_HOME}/files/topology.json" # Destination topology.json file you'd want to write output to
MAX_PEERS=15 # Maximum number of peers to return on successful fetch
CUSTOM_PEERS="x.x.x.x:6000|relays-new.cardano-mainnet.iohk.io:3001:2"
ok, wait 1 sec, looks fine