Processed TX is 0_

Hi,

The processed TX is displaying as 0.

Would anyone have any suggestions?

Thanks,
Skenny

On your BP or relay(s)?

On both my BP and relay

Could you show us the topology-files of both your BP and relay? Please mask the IP of your BP though.

Screenshot from 2021-03-17 18-32-05

I assume that it the topology-file of your relay? Your relay should be able to be accessed by the network, so you need to have a lot more entries in the topology-file of your relay.

Have a look at this guide Guide: How to build a Cardano Stake Pool - CoinCashew, especially section 14.

Man, u have 0 tx because u are not running topology updater script
U can check if ur port is open

from BP
telnet relay_IP Relay_port

from Relay
telnet BP_IP BP_port

U should see connected; if not check the fw

On ur BP u should have

sudo ufw allow proto tcp from Relay_IP to any port BP_port

On Relay
sudo ufw allow proto tcp from any to any port Relay_port

Cheers,

Hi,

Everything looks ok with them commands Alex.

I had to restart the aws instances today so IP chnaged, Would I need to reregister the pool?

Here is a pic of the replay topology file.

Thanks,
Steven

Aaa ok, of course… u need to register again the relay with the new IP

Do we have to register the stake keys and stake pool?

So what steps in the coincashew guide?

here is a link to the guide: https://www.coincashew.com/coins/overview-ada/guide-how-to-build-a-haskell-stakepool-node

Thanks,
Skenny

Register the pool again without paying 500ADA
Step 12


cardano-cli stake-pool registration-certificate \
    --cold-verification-key-file $HOME/cold-keys/node.vkey \
    --vrf-verification-key-file vrf.vkey \
    --pool-pledge 100000000 \
    --pool-cost 345000000 \
    --pool-margin 0.15 \
    --pool-reward-account-verification-key-file stake.vkey \
    --pool-owner-stake-verification-key-file stake.vkey \
    --mainnet \
    --single-host-pool-relay <dns based relay, example ~ relaynode1.myadapoolnamerocks.com> \
    --pool-relay-port 6000 \
    --metadata-url <url where you uploaded poolMetaData.json> \
    --metadata-hash $(cat poolMetaDataHash.txt) \
    --out-file pool.cert

1 Like

Hi Alex,

Would an Elastic IP Address work better if the instance decides to stop and start again? saves re-registering every time there is a problem with the instance and the public IP changing.

Thanks
Nico

should be fine, but why you don’t take a static IP?

Yeah, could do that, but just wondering for reliability and reachability.
Thanks

static IP is ok, it will be reachable from all world and it will not change when the server reboot

1 Like

Hello Alex

i change port of relay node and block producer node. and then, i update my certificate and submit it but for now i can’t get process tx and mempool tx.

can you help me about this problem ?

by the way, i can telnet from block producer to relay and then from relay to block producer node

What is ur ticker?

Nobi, Alex
i have executed topology updater about 4 times but not get yet process tx and mempool tx

ok, and the topology updater should run on relay once/hour right?
what is the last message received from topology updater?

can u show me the glive output for Relays?

Cheers,

yes, of course
unfortunately, i use cronjob, Alex
i can’t see output of my crobjob but it should be fine for the output of topologyupdater.sh