topologyUpdater is it working on TESTNET? How much time takes to be added to the list..?

Hi guys, I am trying to set my topology through the topologyUpdater script (I am on TESTNET)… I run the script every hour and get the message back… but when I try to fetch the topology file after 5+ hours I get the message: “IP is not (yet) allowed to fetch this list”… don’t know why… is it possible that it takes more than one day of running the script to be added to the list…?


{ "resultcode": "201", "datetime":"2021-07-08 00:41:13", "clientIp": "xx.xx.xx.xx", "iptype": 4, "msg": "nice to meet you" }
{ "resultcode": "204", "datetime":"2021-07-08 04:32:15", "clientIp": "xx.xx.xx.xx", "iptype": 4, "msg": "glad you're staying with us" }
{ "resultcode": "204", "datetime":"2021-07-08 05:45:11", "clientIp": "xx.xx.xx.xx", "iptype": 4, "msg": "glad you're staying with us" }
{ "resultcode": "204", "datetime":"2021-07-08 06:47:03", "clientIp": "xx.xx.xx.xx", "iptype": 4, "msg": "glad you're staying with us" }
{ "resultcode": "204", "datetime":"2021-07-08 07:47:03", "clientIp": "xx.xx.xx.xx", "iptype": 4, "msg": "glad you're staying with us" }
{ "resultcode": "204", "datetime":"2021-07-08 08:47:03", "clientIp": "xx.xx.xx.xx", "iptype": 4, "msg": "glad you're staying with us" }

If I try to fetch the topology file/list I get:

{ "resultcode": "402", "datetime":"2021-07-08 08:57:04", "clientIp": "xx.xx.xx.xx", "iptype": 4, "msg": "IP is not (yet) allowed to fetch this list",  "Producers": [   { "addr": "BP-node-ip", "port": xxxx, "valency": 1 } ,
  { "addr": "relays-new.cardano-testnet.iohkdev.io", "port": 3001, "valency": 2 } ,
  { "addr": "buddy-relay-ip", "port": xxxxx, "valency": 1 } , { "addr": "relays-new.cardano-mainnet.iohk.io", "port": 3001, "valency": 2 } ]  }

(that list is my customPeers I added, although the last one is added in the response and not from me… is weird because is iohk relays but mainnet…)

you will need to use the NWMAGIC for testnet… .

also the servers are synced? if not they will not connect to each other

Yes I found the issue 2 min after creating this post… the NWMAGIC was in the first curl but was missing in the fetch one… now it works!! Already have my producers added and restarted the node… a question: do I have to continuously ping/curl the endpoing every hour to be always added to the list…? or now that I am added… the service will automatically check that I am “available” for other peers?? And I only need to hit the “fetch endpoint” when I need to update again my own topology file…

The topologyUpdater shell script must be executed on the relay node 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.

!> Note: You should NOT set up topologyUpdater for your block producing nodes.

And I only need to hit the “fetch endpoint” when I need to update again my own topology file…

Exactly, before to restart the node which is recommanded once/24 hours… but it’s not a must

Cool, so If I understood correctly, the only thing I need to do from now on is fetch a new topology/producers-list every 24hours more or less… but nothing else…

They automatically ping me to see that I am online etc… I don’t have to ping them…right?

right :slight_smile: all u have to check is the topology updater script… and to monitor the IN peers, without IN peers you will not process TX