# Relay node setup completed but Processed TX : 0 (no transactions processed) **URL:** \ **Category:** Operate a Stake Pool\ **Created:** [8 December 2020 13:39 UTC](https://forum.cardano.org/t/relay-node-setup-completed-but-processed-tx-0-no-transactions-processed/42946 "2020-12-08T13:39:54Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Alexd1985](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.cardano.org/alexd1985/32/23759_2.png) [@Alexd1985](https://forum.cardano.org/u/Alexd1985)\ **Post date:** [8 December 2020 13:39 UTC](https://forum.cardano.org/t/relay-node-setup-completed-but-processed-tx-0-no-transactions-processed/42946/1 "2020-12-08T13:39:54Z")
Hello new Pool Operators! Today I want to share with you a possible way to fix the issue: relays node setup completed but Processed TX : 0 (no transactions processed). If you are new you must know that after the node was started for the first time, you need to sync it with the network. When the sync has been completed, you need to announce your Relays into the network and this will be done with topologyupdater script (the test network has to get along without the P2P network module for the time being, it needs static topology files. This “TopologyUpdater” service, which is far from being perfect due to its centralization factor, is intended to be a temporary solution to allow everyone to activate their relay nodes without having to postpone and wait for manual topology completion requests.) > **[3,927 commits this week - Cardano Updates](https://cardanoupdates.com/)** > > Cardano releases and daily development reports at 00:00 (UTC). See commits in real-time. !!! The topologyupdater shell script must be executed on the relay node as a cronjob 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 !!! ( Another important thing could be that u are using IPv6 and u have to change the node arguments ![image](https://us1.discourse-cdn.com/flex023/uploads/cardano/original/3X/3/a/3aa604a57a8433caba4d6bb8b6c5e6828afedd5d.jpeg) Also u need to edit your topologyupdater script # if you run your node in IPv4/IPv6 dual stack network configuration and want announced the # IPv4 address only please add the -4 parameter to the curl command below (curl -4 -s …) Eg: curl -4 -s "[https://api.clio.one/htopology/v1/?port=$](https://api.clio.one/htopology/v1/?port=%24)… ) If you look in logs/topologyupdater.log file you will see: - first 3 requests (after 2 hours) will generate: { “resultcode”: “x”, “datetime”:“2020-12-08 11:13:02”, “clientIp”: “your\_node\_ip”, “iptype”: 4, “msg”: “nice to meet you …” } - 4th consecutive request (after 3 hours) will generate: { “resultcode”: “204”, “datetime”:“2020-12-08 11:13:02”, “clientIp”: “your\_node\_ip”, “iptype”: 4, “msg”: “glad you’re staying with us” } each time the script runs your topology.json file will be overwritten with new relays (REMEMBER to edit your BP\_IP in topologyupdater script → CUSTOM\_PEERS ) ALSO the topologyupdater script must run only on Relay nodes! !!! if your CNODE\_PORT is blocked by FW for incoming connections you will received the following message in topologyupdater.log file: { “resultcode”: “403”, “datetime”:“2020-12-06 08:11:03”, “clientIp”: “x.x.x.x”, “iptype”: 4, “msg”: “glad you want to stay with us, but please check and enable your IP:port reachability” } at this point you need to check the FW (sudo ufw status) to see if the CNODE\_PORT which has been set in env file is open and permit incoming connections. (sometimes port-fowarding needs to be configured if private IPs are used) you can check here [https://www.portcheckers.com/](https://www.portcheckers.com/) (or from which site you wish) * * * Now, if all looks good (topologyupdater.log and topology.json files)you can check with ./gliveview.sh to see your nodes statistics and should be like this: ![image](https://us1.discourse-cdn.com/flex023/uploads/cardano/original/3X/6/2/62cdb46dd3520d84d92aa9b32c5aed36ab131e1a.png) As you can see you have informations about the type of node (BP or Relay), about epoch status, up-time, peers and the most important I think Processed TX This should not be 0 , it should increase!!! Now if Processed TX are increasing that means your node communicating fine with nodes discovered and updated in topology.json file. BUT if Processed TX NOT increasing means something is wrong and you need to investigate if in gliveview looks like this, this means the relays from topology files don’t know you or can’t communicate with your node ![image](https://us1.discourse-cdn.com/flex023/uploads/cardano/original/3X/5/3/536f7e70335b7ea87dd0445eba505259e9b8a2aa.jpeg) as you can see everything looks fine except [IN] PEERS (here is just the BP connected) already agreed that in topologyupdater.log files you are receiving the following message: { “resultcode”: “204”, “datetime”:“2020-12-08 11:13:02”, “clientIp”: “your\_node\_ip”, “iptype”: 4, “msg”: “glad you’re staying with us” } (if not check your topologyupdater script!) At this point you need to check why the nodes from topology.json file are not able to make connections with you. One possible reason could be that your node is not known by them… and you must check if your node was added in the mainnet cardano relays topology file here: [https://explorer.mainnet.cardano.org/relays/topology.json](https://explorer.mainnet.cardano.org/relays/topology.json) If your node is not present that means something went wrong when you registered, and could be that your metadata HASH has been corrupted and don’t mach. Using the following command, I was able to see that SMASH calculated the hash of the meta but that didn’t match the hash stated in the registration certificate (obviously swap out my pool ID for your own) curl [https://smash.cardano-mainnet.iohk.io/api/v1/errors/00333b89543da962cc92e7ffa45848f42a98f7276780670728ce5256](https://smash.cardano-mainnet.iohk.io/api/v1/errors/00333b89543da962cc92e7ffa45848f42a98f7276780670728ce5256) if your hash is ok the output will be if your hash is NOT ok the output will be something like: [{“time”:“08.12.2020. 13:13:42”,“retryCount”:18,“poolHash”:“ad198e1148b9cb1ccdbc935b00074e82eaf73a29e233095ad6bd25fdd7b2d7a0”,“cause”:"Hash mismatch from poolId ‘00333b89543da962cc92e7ffa45848f42a98f7276780670728ce5256’ when fetching metadata from ‘https://url\_where\_you\_uploaded/metadata.json’… Incidentally, you can also check that SMASH can see your meta with the following: curl [https://smash.cardano-mainnet.iohk.io/api/v1/metadata/[your-pool-id-hash]/[your-pool-meta-data-hash]](https://smash.cardano-mainnet.iohk.io/api/v1/metadata/%5Byour-pool-id-hash%5D/%5Byour-pool-meta-data-hash%5D) If there’s a match, it will echo back the contents of your meta file. If you get nothing back, SMASH doesn’t know you. Try to upload again the metadata.json file and be carefuller to not change anything because also the HASH will change and will NOT match! IF HASH is ok after you uploaded the metadata again, you should see in gliveview: ![image](https://us1.discourse-cdn.com/flex023/uploads/cardano/original/3X/7/7/77681bc40b2784f357e941e5034e2de2b43dfb06.png) This means you are now ready to create BLOCKS! GOOD LUCK! I met another case this days when the Relay had IN / OUT PEERS but no tx incrementing .. this was fixed by editing the configuration.json file TraceLocalTxSubmissionProtocol”: false, → true “TraceLocalTxSubmissionServer”: false, → true FOR BP tsoot check: > [@How we can check if BP is ready to create BLOCKS](https://forum.cardano.org/t/how-we-can-check-if-bp-is-ready-to-create-blocks/42891): > > Hello Cardano Pool Operators! Today I want to give you few tips which helps new Pools Operators to identify if the node is working as a BP and ready to produce BLOCKS or as a Relay (1.23.0 version): As you already know starting with version 1.23.0 the Liveview mode is not available anymore… but how can you identify that BP is working well? !!! At this step your POOL should be already registered with success into the network and the KEYS/CERTIFICATES/etc were created in /cnode/priv/pool/your\_f… I hope this will be useful for the new Pool Operators. #################################################### # Thank you and if you want to support us please delegate with # Charity Pool ticker: CHRTY # Earn rewards by helping others! Support children education! # Support decentralization! #################################################### ---
**Author:** ![Halit\_Sawangsaensuk](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.cardano.org/halit_sawangsaensuk/32/23472_2.png) [@Halit\_Sawangsaensuk](https://forum.cardano.org/u/Halit_Sawangsaensuk)\ **Post date:** [12 December 2020 02:51 UTC](https://forum.cardano.org/t/relay-node-setup-completed-but-processed-tx-0-no-transactions-processed/42946/2 "2020-12-12T02:51:49Z")
Hi sir, I was mistake by using deploy-as-systemd.sh script([https://cardano-community.github.io/guild-operators/#/Scripts/topologyupdater](https://cardano-community.github.io/guild-operators/#/Scripts/topologyupdater)) to activate TopologyUpdater in core node. But, I don’t want my topology.json file fecth and refresh all time.(need to fix and sync with my relay only). Therefore, I would like you to please help me, How to stop TopologyUpdater? . ---
**Author:** ![Alexd1985](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.cardano.org/alexd1985/32/23759_2.png) [@Alexd1985](https://forum.cardano.org/u/Alexd1985)\ **Post date:** [12 December 2020 08:02 UTC](https://forum.cardano.org/t/relay-node-setup-completed-but-processed-tx-0-no-transactions-processed/42946/3 "2020-12-12T08:02:15Z")
To check the status Sudo systemctl status topologyupdater. To stop the service sudo systemctl stop topologyupdater To disable it sudo systemctl disable topologyuodater ---
**Author:** ![Halit\_Sawangsaensuk](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.cardano.org/halit_sawangsaensuk/32/23472_2.png) [@Halit\_Sawangsaensuk](https://forum.cardano.org/u/Halit_Sawangsaensuk)\ **Post date:** [12 December 2020 08:03 UTC](https://forum.cardano.org/t/relay-node-setup-completed-but-processed-tx-0-no-transactions-processed/42946/4 "2020-12-12T08:03:12Z")
> [@Alexd1985](#): > > Sudo systemctl status topologyupdater Thank you very much ---
**Author:** ![oskanaan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.cardano.org/oskanaan/32/24482_2.png) [@oskanaan](https://forum.cardano.org/u/oskanaan)\ **Post date:** [21 December 2020 17:07 UTC](https://forum.cardano.org/t/relay-node-setup-completed-but-processed-tx-0-no-transactions-processed/42946/5 "2020-12-21T17:07:36Z")
Would you be able to have a look at this question please? I’ve been struggling with processed count to increase. > [@Processed TX is 0](https://forum.cardano.org/t/processed-tx-is-0/43496): > > Hi, This has been raised before in other posts, I’ve checked those but dont think my issue is the same, I’ve tried to check my configuration based on the solutions provided with no luck. I’ve recently setup my pool, and can see incoming and outgoing connections from my relay, plus 1 incoming/outgoing connection to the relay from the producer. However, up until now I havent seen the Processed Tx number increasing in both relay and producer. Here is what I’ve checked up until now: The relay po… ---
**Author:** ![conniec1](https://avatars.discourse-cdn.com/v4/letter/c/c0e974/32.png) [@conniec1](https://forum.cardano.org/u/conniec1)\ **Post date:** [26 March 2021 17:26 UTC](https://forum.cardano.org/t/relay-node-setup-completed-but-processed-tx-0-no-transactions-processed/42946/6 "2021-03-26T17:26:10Z")
I have same problem, Now I have the producer TX increase but relay TX is 0. I changed from DNS ip to straight number ip address, and try to telnet between BP and relay. ---
**Author:** ![cyberruss](https://avatars.discourse-cdn.com/v4/letter/c/4bbf92/32.png) [@cyberruss](https://forum.cardano.org/u/cyberruss)\ **Post date:** [21 October 2021 23:01 UTC](https://forum.cardano.org/t/relay-node-setup-completed-but-processed-tx-0-no-transactions-processed/42946/7 "2021-10-21T23:01:12Z")
> [@Alexd1985](#): > > I met another case this days when the Relay had IN / OUT PEERS but no tx incrementing … this was fixed by editing the configuration.json file > > TraceLocalTxSubmissionProtocol”: false, → true > “TraceLocalTxSubmissionServer”: false, → true Also requires: “TraceMempool”: true,