What does this mean? My local node is fully caught up. {"file":"acctupdates.go","function":"github.com/algorand/go-algorand/ledger.(*accountUpdates).lookupWithRewards","level":"error","line":1834,"msg":"[Stack] goroutine 129 [running]:\nruntime/debug.Stack(0x853ca180, 0x851867a8, 0x8a4c02c0)\n\tru…

Is your node an archival node or a relay? Did you use fast catchup? If you answer yes to both questions, this is most likely the issue: fast catchup cannot be used with an archival node or a relay.

The issue was that my local env var was set to a slightly outdated catchup, I manually set the catchup to use the latest and Im guessing this will fix it. Thanks for the help fabrice :slight_smile:

Hmm this didnt seem to solve my issue. My node is caught up with the latest block but Im still getting the error in the title: pi@raspberrypi:~/node $ ./goal node status -d ~/node/mainnetdata -w 1000 Last committed block: 16525128 Time since last block: 4.3s Sync Time: 0.0s Last consensus protocol:…

Just to update here, Nick popped into the discord with this issue and didn’t yet have any disk attached. Will try again once he does.

Node online but keep getting "database round 205862 is behind in-memory round 16927043"

General

nickeleres September 29, 2021, 10:16pm 6

Yep, thanks barnji bra

Topic		Replies	Views
Fast Catchup not working for our node on MainNet	53	5460	October 7, 2020
Can't get my participation node to sync with the blockchain General	9	1337	June 30, 2021
Mainnet participant node syncing problem mainnet , noderunner	3	752	December 13, 2021
Can't complete catchup operation on mainnet -- timeout after 45 minutes (~4m accounts) General	13	1472	November 10, 2020
Node start and stop errors	31	3127	June 14, 2021

Node online but keep getting "database round 205862 is behind in-memory round 16927043"

Related topics