Astar
Astar copied to clipboard
Astar v5.33.0 node crashes with "State already discarded for" after a restart during early sync
Description
I was following this guide to enable EVM debug_ support on a node.
When starting a new node and restarting if during early sync the following error occurred and the node stops. This happen for each restart.
Steps to Reproduce
Replace the example steps below with actual steps to reproduce the bug you're reporting.
- Setup a new machine
- Download the client binary from https://github.com/AstarNetwork/Astar/releases/download/v5.33.0/evm-tracing-artifacts-v5.33.0.tar.gz
- Start the client. I used these arguments
--node-key-file /home/polkadot/node-key --chain astar
--state-pruning archive --blocks-pruning archive --runtime-cache-size 16 --max-runtime-instances
32 --rpc-max-request-size 1 --rpc-max-response-size 24 --rpc-max-connections
3000 --in-peers 20 --out-peers 40 --rpc-external --rpc-port 9933 --rpc-cors
all --rpc-methods unsafe --prometheus-external --enable-evm-rpc -- --sync warp
- Let the client run for a while.
- Stop and start the client (restart)
- The error occurs and the node cannot start anymore.
Environment
- Operating system: Ubuntu jammy
- Project version/tag: v5.33.0
Logs, Errors or Screenshots
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 Astar Collator
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 ✌️ version 5.33.0-4f1b31319f4
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 ❤️ by Stake Technologies <[email protected]>, 2019-2024
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 📋 Chain specification: Astar
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 🏷 Node name: fearless-smile-0003
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 👤 Role: FULL
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 💾 Database: RocksDb at /home/polkadot/.local/share/polkadot/chains/astar/db/full
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 Parachain id: Id(2006)
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 Parachain Account: 5Ec4AhPW97z4ZyYkd3mYkJrSeZWcwVv4wiANES2QrJi1x17F
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 Parachain genesis state: 0x000000000000000000000000000000000000000000000000000000000000000000de2e3567ab0b52f4d9bca7efadf6e7bfe0f453c356d0a7962e4227cfaefe5ab403170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400
Mar 11 07:49:58 juju-1dc0b3-1 polkadot[707361]: 2024-03-11 07:49:58 Is collating: no
Mar 11 07:50:02 juju-1dc0b3-1 polkadot[707361]: Error: Service(Application(Application(Blockchain(RuntimeApiError(UnknownBlock("State already discarded for 0x1d02ef87d5d2ff61fa51d7eaa1ee2c04193d30ba01225e9da697a9c2d5d06af2"))))))
Additional Information
I'm not sure if this is isolated to the tracing binary and I don't think this happens every time.
Please check the arguments you're using.
You seem to be missing:
--ethapi=txpool,debug,trace \
--wasm-runtime-overrides /var/lib/astar/wasm \
Make sure to have folder with wasm overrides.
Please check the arguments you're using.
You seem to be missing:
--ethapi=txpool,debug,trace \ --wasm-runtime-overrides /var/lib/astar/wasm \Make sure to have folder with wasm overrides.
I experienced the same issue when setting these values and I thought I would test without them which is the setup I posted.
Maybe I didn't set --ethapi=txpool,debug,trace but do you think it would prevent this error?
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.