Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Archive] Gnosis archive sync hangs on BeaconHeaders after "minimumLength ('-192') must be a non-negative value" error #6960

Closed
kamilchodola opened this issue Apr 29, 2024 · 0 comments · Fixed by #7058
Assignees

Comments

@kamilchodola
Copy link
Contributor

Started a Gnosis archive node sync.
All was going smooth on stage before actual processing (beaconHeaders) but after a while I got an exception:

System.ArgumentOutOfRangeException: minimumLength ('-192') must be a non-negative value. (Parameter 'minimumLength')
Actual value was -192.
   at System.ArgumentOutOfRangeException.ThrowNegative[T](T value, String paramName)
   at System.ArgumentOutOfRangeException.ThrowIfNegative[T](T value, String paramName)
   at System.Buffers.SharedArrayPool`1.Rent(Int32 minimumLength)
   at Nethermind.Synchronization.FastBlocks.HeadersSyncFeed.BuildDependentBatch(HeadersSyncBatch batch, Int64 addedLast, Int64 addedEarliest) in /_/src/Nethermind/Nethermind.Synchronization/FastBlocks/FastHeadersSyncFeed.cs:line 459
   at Nethermind.Synchronization.FastBlocks.HeadersSyncFeed.InsertHeaders(HeadersSyncBatch batch) in /_/src/Nethermind/Nethermind.Synchronization/FastBlocks/FastHeadersSyncFeed.cs:line 593
   at Nethermind.Synchronization.FastBlocks.HeadersSyncFeed.HandleResponse(HeadersSyncBatch batch, PeerInfo peer) in /_/src/Nethermind/Nethermind.Synchronization/FastBlocks/FastHeadersSyncFeed.cs:line 389
   at Nethermind.Synchronization.ParallelSync.SyncDispatcher`1.DoHandleResponse(T request, PeerInfo allocatedPeer) in /_/src/Nethermind/Nethermind.Synchronization/ParallelSync/SyncDispatcher.cs:line 186

It appeared 5 times and my progress freezed at:
Beacon Headers from block 1 to block 33647907 | 26,693,985 / 33,647,907 | queue 0 | current 11,718 Blk/s | total 9,047 Blk/s
and was not moving any forward.

As this was on an automated node can't tell if restart helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants