Block producing node always stuck at "starting.." epoch is 0

Thanks a lot! Let me wait and see.!!
In the cronta , there is only one line
22 * * * * /home/ubuntu/cardano-my-node/topologyUpdater.sh

Perfect… now check the logs from topology updater… can u tell me the ticker again?

The ticker is FIRE9
Updater show the following:

{ "resultcode": "201", "datetime":"2021-03-24 16:37:35", "clientIp": "3.142.247.56", "iptype": 4, "msg": "nice to meet you" }
{ "resultcode": "504", "datetime":"2021-03-24 17:22:07", "clientIp": "3.142.247.56", "iptype": 4, "msg": "one request per hour please" }
{ "resultcode": "203", "datetime":"2021-03-24 18:22:08", "clientIp": "3.142.247.56", "iptype": 4, "msg": "welcome to the topology" }
{ "resultcode": "403", "datetime":"2021-03-24 19:22:06", "clientIp": "3.142.247.56", "iptype": 4, "msg": "glad you want to stay with us, but please check and enable your IP:port reachability" }
{ "resultcode": "403", "datetime":"2021-03-24 20:22:08", "clientIp": "3.142.247.56", "iptype": 4, "msg": "glad you want to stay with us, but please check and enable your IP:port reachability" }
{ "resultcode": "204", "datetime":"2021-03-24 21:22:02", "clientIp": "3.142.247.56", "iptype": 4, "msg": "glad you're staying with us" }
{ "resultcode": "204", "datetime":"2021-03-24 22:22:05", "clientIp": "3.142.247.56", "iptype": 4, "msg": "glad you're staying with us" }
{ "resultcode": "204", "datetime":"2021-03-24 23:22:08", "clientIp": "3.142.247.56", "iptype": 4, "msg": "glad you're staying with us" }
~

Ok, looking great (on adapools is also green)… now if u run

./relay-topology_pull.sh

do u see more peers including ur Producer in topology file?

yes, but u ran again the script?

The updater.sh is on the relay, how is the BP have peer increase?

Do u mean IN peers? Press p … there are other public nodes?

I ran again the topology_pull.sh on relay and restart the relay node. The BP always in the mainnet-topology.json as indicated above.

However, BP doesn’t have the topology pull script, how is the peers going to be increase on BP?

That is always I am trying tell, there is no IN peer on BP

image

there are no other public node, only my relay node
image

I ran again the topology_pull.sh on relay and restart the relay node. The BP always in the mainnet-topology.json as indicated above.

How is the topology file now? Do u see the ipv4 of the Producer instead the DNS?

Did u replaced the dns name with the ipv4 address right?

BLOCKPRODUCING_IP=

However, BP doesn’t have the topology pull script, how is the peers going to be increase on BP?

The topology file are for outgoing peers not for IN peers… u don’t see IN peers because your relay don’t initiated one

which topology, the mainnet-topology or the log/topologyupdater?

The mainnet-topology from relay

Did u replaced the dns name with the ipv4 address right?

BLOCKPRODUCING_IP=

No, I did not replace with dns with ipv4, am I suppose to manually change it the ip4 address? in the mainnet-topology? and restart?

Here, did u replaced with ipv4? If no please replace it, save it, run the script again; now in mainnet-topology file u should see the ipv4 of Producer

Restart the node

in the relay node, the mainnet.json file become a generated file , not the original one that I edit,
line come from relay pull.sh
BLOCKPRODUCING_IP=1.1.1.1
Is this correct?

If it’s the Producer IP then yes, but please delete the IP… someone can use it

I did update, save and restart, I see ipv4 of BP in the mainnet.topology

Great… now u should see it (the relay) to IN on Producer

what do you mean delete? delete from the relay_update_pull.sh ? or somewhere?

Delete it from forum… edit the message and write 1.1.1.1

Do not post senditive data for ur producer… like IP hostname, etc on forum

I see. Thanks for advice, however there are some of your reply, I cannot delete, what should I do?