BP node IP addrss change, is it require to register again

I just restarted and type the command, the screen is flashing fast, do you want the beginning of the last?

Exactly, the topology file is not ok

Delete everything and paste


{
  "Producers": [
    {
      "addr": "relays-new.cardano-mainnet.iohk.io",
      "port": 3001,
      "valency": 2
    },
    {
      "addr": "BP_IP",
      "port": BP_PORT,
      "valency": 1
    }
  ]
}

but this topology was updated by the relay_topology_pull.sh, it was originally like what you suggested

Don’t run the script just modify the topology amd restart the node

just restarted, this is after running the command, did not run the relay_topology.sh script
xtended, new tip: cd86de9d9c4802632c6b09513b0243fc42796705f703b6ec212987f06dda175b at slot 3901892
Jul 20 18:44:07 ip-172-31-31-40 cardano-node[1732840]: [ip-172-3:cardano.node.ChainDB:Notice:51] [2021-07-20 18:44:07.81 UTC] Chain extended, new tip: 4b573868011e915ae55847dad4905dba8bbffa67a2757f269413adf6efc9f9d0 at slot 3902778
Jul 20 18:44:09 ip-172-31-31-40 cardano-node[1732840]: [ip-172-3:cardano.node.ChainDB:Notice:51] [2021-07-20 18:44:09.06 UTC] Chain extended, new tip: 9c19cc818d32de29947e69a97602f580437e591714a7ddd208418e2aacebdc16 at slot 3903852
Jul 20 18:44:09 ip-172-31-31-40 cardano-node[1732840]: [ip-172-3:cardano.node.ChainDB:Info:51] [2021-07-20 18:44:09.19 UTC] Valid candidate 3d37cb9a18758e939c1ce68d71bee9836f50bdf948d309597753422eda86d4a4 at slot 3903972
Jul 20 18:44:09 ip-172-31-31-40 cardano-node[1732840]: [ip-172-3:cardano.node.ChainDB:Notice:51] [2021-07-20 18:44:09.19 UTC] Chain extended, new tip: 3d37cb9a18758e939c1ce68d71bee9836f50bdf948d309597753422eda86d4a4 at slot 3903972
Jul 20 18:44:10 ip-172-31-31-40 cardano-node[1732840]: [ip-172-3:cardano.node.ChainDB:Notice:51] [2021-07-20 18:44:10.44 UTC] Chain extended, new tip: c46c0e61d3568d076e4641387be29e6d63c5ce94e5497dd5886aa85d7328c928 at slot 3905137

The gLview come back ,it is still stuck at 11 %

And, any improvements?

it is slightly faster now it is 12%, should I run the relay _topology script?
But it is still 0 IN PEER

In BP glview:
IN Peer have both relay nodes IP show up, including this one
OUT peer only have the other relay node’s iP, but no this node (slow sync, out of sync), why?

Man, wait till the node will be 100% synced
Till then no other nodes will connect

Do not run anything till then

ok, will wait right now is 19% seems normal speed now…
will update…

@Alexd1985
It is fully synced now, on the BP gLview, I still on see one IN peer.
It is not this Relay node that we are trying to fix.
On this relay node, I do see 8 IN PEERs, one of them is the BP.

Ok, did u added the Producer IP inside the pull… script? Or did u allowed on BP to permit connections from the 2nd relay

Yes, I added BP IP inside the relay_topology_pull.sh as we discussed yesterday.
On relay:
BLOCKPRODUCING_IP=x.x.x.x
BLOCKPRODUCING_PORT=6000
curl -4 -s -o /home/ubuntu/cardano-my-node/mainnet-topology.json “https://api.clio.one/htopology/v1/fetch/?max=20&customPeers=${BLOCKPRODUCING_IP}:${BLOCKPRODUCING_PORT}:1|relays-new.cardano-mainnet.iohk.io:3001:2

On BP node, I did add IP of of 2nd relay node in mainnet-topology.json.

That is the way to allow 2nd relay?

On BP : mainnet-topology.json
{
“Producers”: [
{
“addr”: “Relay1 IP”,
“port”: 6000,
“valency”: 1
},
{
“addr”: “Relay2 IP”,
“port”: 6000,
“valency”: 1
}
]
}

Check the firewall rules

From relay try

telnet BP_IP BP_PORT

The firewall rule for BP seems okay,
the telnet from relay node 2 to BP was shown as connected.
Is there anything I missed for adding 2nd relay node?

Now the BP can see 2 peers in and 2 peers out! One thing strange is from RL2 telnet to BP works, but BP to RL2 doesn’t work, do you think this is an issue ?

thanks for your help