my relays and bp were producing transactions then it stopped all of a sudden. ive checked my ports, firewall, ufw, and ive also asked around just incase someone running into the same problem.
everything was fine then it stopped producing transactions. thank you everyone.
Hi Jon,
Are you running at home or on cloud?
Are your nodes in sync (on tip; slot/block height periodically increasing)?
query block height via:
cardano-cli shelley query tip --mainnet
If running from home, is it possible your ip is dynamic and has changed?
Did you ever run version 1.18.1 on on mainnet when d < 1? If so, there’s a good chance the database could be corrupted.
Do you have logging enabled which may give some clues?
Thanks in advance
Your friend, FROG
hey frog
im running it on google cloud.
yes all relays and BP synced with the correct block height.
everything was running great & i was getting a ton of transactions then it all stopped.
it was running great for about 2days then stopped.
i went straight to 1.19.0
The other possibility is that other nodes do not include your nodes in their topology. Do you have a system like topologyupdater.md installed on your relay(s) where you can verify (in this case, every hour in a log file default named topologyUpdater_lastresult.json) that you’re still being given to other relays as a peer?
In our early days we always got the tip moving along fine as soon as we had a proper list of other nodes in our own topology.json … but we didn’t see any transactions in our logfiles until topologyupdater.md had been running successfully for a few hours.
If like @ADAfrog says is possible you might have been on 1.18.1, don’t delete your whole DB directory… just the ledger directory it contains; it’ll made a huge difference in the mount of time it takes to get operational again…
thank you i found out the automatic topology thing kept req update less than an hour apart so it did a temp black list on ip. so i try to redo my nodes and now the script is different from a few days ago so now something is wrong with the path to the cnode. I seen someone with the same post to fix the path but not quite sure how.
Hi @COSDpool, I’m a new SPO and I’m wondering if the topologyUpdater script is still required these days?
Am asking because I cannot see transactions on my pool either (I’m only using the prometheus/grafana metrics)
I own two Pool, one for testnet and one for mainnet, and my pools appear on both https://explorer.cardano.org/relays/topology.json and https://cardano-explorer.cardano-testnet.iohkdev.io/relays/topology.json.
Is that enough?
yes, it’s still required. To see if it’s running properly you can double check the instructions here… there’s a JSON file where it’ll indicate if your connections to their topology service are being refused or if your relays have gotten behind other nodes in syncing the blockchain.
The automatic process that will eventually replace these third party topology management services is called the peer-to-peer-governor:
When topology management is eventually integrated into the Cardano node it will be very big news (you’ll probably see a headline on this forum) but it will also be a big release note in whatever version of cardano-node implements it first, so keep reading the notes for all new releases:
I had something similar happen. I stopped both nodes and deleted the DB folder containing the database and restarted everything. It took around 3 days to rescync but then transactions worked fine ever since.