RoninDojo Logs Troubleshooting
Why should I check logs
Section titled “Why should I check logs”If you are new to RoninDojo and you need to troubleshoot, then are probably thinking “What am I looking looking for?”
Checking logs is always a good first step to troubleshoot and further understand your node!
How to check logs
Section titled “How to check logs”You can view logs by using the RoninUI graphical user interface.
If for some reason this is not an option, then you can use the RoninCLI menus. Here is an example.
Dojo → Logs → Tor
What normal logs look like
Section titled “What normal logs look like”Please take note of what these logs look like, as this indicates a healthy RoninDojo bitcoin node.
You will know the initial block download is complete once you see progress=1.0.
When you see a log line like CreateNewBlock(): block weight: 3992443 txs: 1055 fees: 9989072 sigops 5829, that is an example of the Fee Estimator calling the bitcoind RPC createblocktemplate method in order to calculate fee rates.
It will also show Tor connections to peers, which rotate so you can disregard failed: general failure and failed: connection refused.
The warning= 'xx of last 100 blocks have unexpected version' means the miner that mined the block is running a different version of core than yourself — you can disregard.
This connection closed normally without authentication can safely be ignored as it’s normal behavior.
For your Fulcrum or Electrs indexer, you can expect logs similar to the following.
[INFO electrs::index] indexing 1 blocks: [959616..959616][INFO electrs::chain] chain updated: tip=00000000000000000000eec74314bff05daf67223b96a1a2c3452ac418424d13, height=959616The Node.js logs will display the pubkeys that are being tracked via multiaddr and unspent. It will also display when a new block is mined. The pubkeys displayed are those of your HD public addresses.
Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. can safely be ignored as it’s normal behavior.