hyperledger / besu

An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu
https://www.hyperledger.org/projects/besu
Apache License 2.0
1.43k stars 759 forks source link

Sync Error - Attempt to start an already started synchronizer. #7153

Closed michaels0184 closed 2 weeks ago

michaels0184 commented 1 month ago

besu-config.txt

Description

2 boot nodes, 4 validator nodes, 3 member nodes, 1 rpc node.

Steps to Reproduce (Bug)

  1. Running tests against the BESU network over 3-4 hours

Expected behavior: All validators continue to mine at the same rate

Actual behavior: One validator stops mining and hangs indefinitely.

Frequency: Happens when running tests after a 3-4 hours (12 hours max). This happens every-time we run tests against the network.

Logs (if a bug)

Besu has identified a problem with its worldstate database.

│ # Your node will fetch the correct data from peers to repair the problem. │ # Starting the sync pipeline... #################################################################################################### │ │ validator-4-besu Throwable summary: java.lang.IllegalStateException: Attempt to start an already started synchronizer. │ │ validator-4-besu at: org.hyperledger.besu.ethereum.eth.sync.DefaultSynchronizer.start(DefaultSynchronizer.java:218) │ │ validator-4-besu 2024-05-28 23:58:01.418+00:00 | EthScheduler-Services-7 (importBlock) | ERROR | PipelineChainDownloade │ │ validator-4-besu java.util.concurrent.CompletionException: java.lang.IllegalStateException: Attempt to start an already started synchronizer.

Versions

Additional Information (Add any of the following or anything else that may be relevant)

non-fungible-nelson commented 1 month ago

Hi there - Bonsai and Tessera can have issues together - have you tried FOREST mode for your data storage format?

https://besu.hyperledger.org/development/public-networks/concepts/data-storage-formats

GGos3 commented 2 weeks ago

In my case, I encountered the same issue, but changing the node's option from data-storage-format="BONSAI" to "FOREST" resolved the error.