Giters

futureversecom / trn-seed

Implementation of The Root Network node in Rust, based on the Substrate framework.

Home Page:https://www.therootnetwork.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Root mainnet synchronization issue

jinseon2416 opened this issue · comments

commented

Release

Release Name: 5.48.0

Spec Version: 48

Client Version: 5.0.0

We operated the mainnet with source code according to the trn-seed guide. However, the same thing happens with block number 8260096. Could I please receive an update on what is being done about this issue?

The execution command is as follows:

seed --chain=root --base-path=/data/root-mainnet --rpc-cors=all --rpc-external --ws-external

2024-01-24 23:46:14 ⚙️  Syncing  0.0 bps, target=#10395153 (9 peers), best: #8260344 (0x3a03…720d), finalized #8260096 (0x1508…f452), ⬇ 691.3kiB/s ⬆ 0.8kiB/s
2024-01-24 23:46:19 ⚙️  Syncing  0.0 bps, target=#10395154 (9 peers), best: #8260344 (0x3a03…720d), finalized #8260096 (0x1508…f452), ⬇ 691.6kiB/s ⬆ 0.8kiB/s
2024-01-24 23:46:24 ⚙️  Syncing  0.0 bps, target=#10395156 (9 peers), best: #8260344 (0x3a03…720d), finalized #8260096 (0x1508…f452), ⬇ 691.0kiB/s ⬆ 0.4kiB/s
2024-01-24 23:46:29 ⚙️  Syncing  0.0 bps, target=#10395157 (9 peers), best: #8260344 (0x3a03…720d), finalized #8260096 (0x1508…f452), ⬇ 693.5kiB/s ⬆ 1.2kiB/s
2024-01-24 23:46:34 ⚙️  Syncing  0.0 bps, target=#10395158 (9 peers), best: #8260344 (0x3a03…720d), finalized #8260096 (0x1508…f452), ⬇ 726.5kiB/s ⬆ 12.5kiB/s
2024-01-24 23:46:37 panicked at 'Digest item must match that calculated.', /home/yanggao/.cargo/git/checkouts/substrate-7e08433d4c370a21/a3ed011/frame/executive/src/lib.rs:520:13
^C2024-01-24 23:47:45 ⚙️  Syncing  0.0 bps, target=#10395159 (9 peers), best: #8260344 (0x3a03…720d), finalized #8260096 (0x1508…f452), ⬇ 49.6kiB/s ⬆ 0.2kiB/s
2024-01-24 23:48:00 Block prepare storage changes error: Error at calling runtime api: Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed
WASM backtrace:

    0: 0x41cd90 - <unknown>!rust_begin_unwind
    1: 0x9b68 - <unknown>!core::panicking::panic_fmt::he11703d1a35eb9c9
    2: 0x3abeb4 - <unknown>!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::execute_block::h8ad92182f35cf449
    3: 0x307b2b - <unknown>!Core_execute_block
commented

hi @jinseon2416, what kind of node are you trying to run? full node or archive node?

btw, can you please update the issue title, it's not relevant to the content of the issue.

commented

hi @ken-centrality, I'm trying to configure an archive mainnet.
The following phenomenon occurs when users run the mainnet as is on GitHub.

commented

thanks @jinseon2416, can you please try adding --sync warp flag to see if it resolves the issue?

commented

@ken-centrality, Block synchronization progressed normally, but rpc queries for previous blocks rather than the latest block do not seem to be working. Can you check this too?

curl http://localhost:9933 -X POST -H "Content-Type: application/json" --data '{"method":"eth_getBlockByNumber","params":["0x9ba3c0",false],"id":1,"jsonrpc":"2.0"}

{"jsonrpc":"2.0","error":{"code":-32603,"message":"Expect block number from id: BlockId::Number(10200000)"},"id":1}

commented

hey @jinseon2416, you will need to wait for at least 48 hours for the node to sync up the old blocks. If it doesn't work, you can try download the snapshot https://s3.ap-southeast-2.amazonaws.com/snapshots.cicd.rootnet.app/snapshots/archive.rootnet/fv-au-prod-snapshot-archive.snapshot.20231122.1700614895.tar.gz, unzip and replace the chains folder with then start the node with --pruning archive instead.

commented

@ken-centrality, I synchronized using a snapshot and it worked normally. Thank you for your kind reply!