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…

The above issue was addressed in [image] TestNet and MainNet Update: 3.2.2 Announcements MainNet and TestNet have been updated to 3.2.2 today, Wed Dec 15, 2021 10:30AM EST (3:30PM UTC). This release does not contain a consensus upgrade. [GitHub Logo] Change…

Hi Cryptocurv, 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. …

Hi Ben, 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 ra…

Hi Ben, i’ve got the same issue… in logs everything seems ok The result i see is just dramatic drop in traffic and connections. But the nodes seems to be synchronized and shows the correct block even little before the algoexplorer with watch goal node status

Hi Scholtz, Is your node a participant node? If so, is your pending txns increasing?

it is archival relay node pending txns does not increase [image]

Can you quantify dramatic drop? 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

[image] Perhaps its just because i restarted it in 2 months… Also for few minutes it was probably not synchronized. Btw, this is my kubernetes setup AlgorandNodes/statefulset.yaml at main · scholtz/AlgorandNodes · GitHub

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 ( Me…

Node sync time keeps increasing - ver 3.2.1

tsachi December 15, 2021, 5:46pm 13

The above issue was addressed in

Topic		Replies	Views
Mainnet participant node syncing problem mainnet , noderunner	3	739	December 13, 2021
Algorand node not syncing v3.9.4 General	1	560	October 2, 2022
Node not syncing after months of inactivity	8	430	January 3, 2021
Cannot get node to sync General noderunner	1	466	April 15, 2022
Can't get my participation node to sync with the blockchain General	9	1330	June 30, 2021

Node sync time keeps increasing - ver 3.2.1

Related topics