Hi,
I am attempting to sync a base-mainnet node (reth backend for both l1 and l2) with magi.
I downloaded the reth chain archive snapshot from base's website, and the reth node starts OK, but when I restart magi, I see in the logs:
Sep 09 19:39:01 start_magi.sh[3711]: [Mon, 9 Sep 2024 19:39:01] INFO: magi at bin/magi.rs:28 Starting Magi. sync mode=full, network=base
Sep 09 19:39:01 start_magi.sh[3711]: [Mon, 9 Sep 2024 19:39:01] INFO: magi::driver at src/driver/mod.rs:88 starting from head: 0xbcf07afe87ff898f2e2782efb034a39cf3b8a039cf43faaf63431745ac84>
Sep 09 19:39:01 start_magi.sh[3711]: [Mon, 9 Sep 2024 19:39:01] INFO: magi::rpc at src/rpc/mod.rs:144 rpc server started at port 9545
Sep 09 19:39:01 start_magi.sh[3711]: thread 'tokio-runtime-worker' panicked at src/l1/chain_watcher.rs:200:58:
Sep 09 19:39:01 start_magi.sh[3711]: range end index 196 out of range for slice of length 164
Sep 09 19:39:01 start_magi.sh[3711]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
and then there is no output after that; it may be the logging (seems like the verbose is too verbose, but INFO level logs are a little lacking) The process stays running, but it has little (under 15 meg) RAM usage and very little CPU, so I am suspicious the watcher thread died but left the process up.
Hi,
I am attempting to sync a base-mainnet node (reth backend for both l1 and l2) with magi.
I downloaded the reth chain archive snapshot from base's website, and the reth node starts OK, but when I restart magi, I see in the logs:
and then there is no output after that; it may be the logging (seems like the verbose is too verbose, but INFO level logs are a little lacking) The process stays running, but it has little (under 15 meg) RAM usage and very little CPU, so I am suspicious the watcher thread died but left the process up.