ok, this is looking good, you also have peers and tx processing
ok, that’s why you don’t see relay 2 on your BP, because is not synced.
do u see any tx transactions on BP now?
Makes sense. So does processed TX and mempool show up at the end of the epoch? Also it’s occasionally saying 2 out and 1 in, what would the second out be, is that the unsynced relay flashing in and out?
No TX on the BP
if you press P in glive you will see the IP of peers; try and check which one is connected and which one flapping
just checked, that’s exactly what it is, the syncing relay popping in and out of the peers out
now… why u are not seeing tx processing in Producer? u should see if u are connected with the working relay
pressing p says working relay in and out are both connected
ok, now go to working relay and press P on glive… do you see the Producer IP to IN and out ?
although… The in port on the producer looking at relay on glive shows the wrong port
out should be 6001 and in should be a random port
got it, yes out is that and in is random. glive peers on the working relay doesn’t show my producer in the outs but it does show it coming in on a random port.
did u tried to change the page with arrow right/left from the keyboard?
I did, and it’s not on any of the pages
ok, then go to topology updater script and check
nano topologyUpdater.sh and check again the custom peers line…
you can also go to topology file and check nano topology.json and check if your Producer is present
it’s there and so is the correct port. I have it beginning with “producer …” which is a little different than the example
so i noticed there was a topology updater.tmp file and I went ahead and deleted that, result was that it added another peer to the in section on my glive for my producer.
giving relay a restart
Still showing that my relay IP exist with 2 instances on my glive view on my produce
Restarting producer…
now it’s not showing any relays coming in - which is more accurate to what’s happening on the processed TX display
Once again using Telnet triggered the relay to show up in the producer
quitting telnet removed the connection from the producer
checking topology
Could it be that I need to wait till my other relay syncs before I’m up and running with the working relay? In other words if A is true and B is false than A and B are false? - because my topology file on my BP does have both relays in there
Man, what ?.. to custom peers add only the IP and port of the Producer… why I see the word producer?
haha. Because the guide I was following said “producer ip:port” so I replaced Ip with the Ip and port with the port and left producer.
changing topology and restarting node… that’s embarrasing
would you look at that
Perfect, now u see tx processing?