My (non-archival, participant) node was running fine for a couple of days. Then, ‘Sync time’ in ‘goal node status’ has started increasing. I did various troubleshooting as follows but the same problem is still there. Can someone help me?
To not cause any impact on mainnet, changed the node status to offline
In config.json, set “DNSSecurityFlags”: 0 and “EnableBlockServiceFallbackToArchiver”: false
This is due to a (benign) bug in the catchup logic. It should not affect the actual catchup or agreement. Regardless, it has been fixed and V3.2.2 has been prepared and I expect it to go to BetaNet Monday with a stable release coming another 48 hours later.
What would you recommend to check if my node is participating without an issue?
For example, is there a way to know if my node is misbehaving or not with regard to being ‘dishonest’ or ‘penalized’? When the issue started, I noticed bunch of pending txns on my node - goal node pendingtxns.
You can look through the logs to see that its keeping up to date and processing transactions correctly.
The node is definitely not being dishonest, though it may be attempting to request block more frequently than it needs to.
There is no concept of penalization besides the possibility of being ranked lower on a peer list by another node if your node is slow to return blocks.
The bug in question should only affect the nodes recognition that catchup is completed. The effect is that the sync counter keeps increasing and it requests more blocks than it needs to
Small remark: since your node is apparently not a relay, it should be not ranked. As @Ben explained, participation nodes are currently not penalized @Cryptocurv .
However, it is very important for the network that participation nodes work properly.
You can either check the logs or use AlertHub (Metrika AlertHub) to monitor your node.
