Thread 'tokio-runtime-worker' panicked about moonbeam

[gdzien-co]

Tried running with debugging options I've seen in #541
-l state-db=trace,sync=trace

It has changed nothing, seems like something in my data is corrupted, will try to run other node with other data location, keeping those for a week or so in case if you need the data files to investigate further.
Log file from docker logs of "new container with old data" attached:
log.txt

[crystalin]

Thank you for trying.
The parameter you typed looks good, but the output should look like those (where you see the log level in the line, like INFO, TRACE...)

2021-07-12 17:46:16.383  INFO main sc_cli::runner: Moonbeam Parachain Collator
2021-07-12 17:46:16.384  INFO main sc_cli::runner: ✌️  version 0.9.2-c25242f8-x86_64-linux-gnu
2021-07-12 17:46:16.384  INFO main sc_cli::runner: ❤️  by PureStake, 2019-2021
2021-07-12 17:46:16.384  INFO main sc_cli::runner: 📋 Chain specification: Moonbase Alpha
2021-07-12 17:46:16.384  INFO main sc_cli::runner: 🏷 Node name: tricky-crate-7940
2021-07-12 17:46:16.384  INFO main sc_cli::runner: 👤 Role: FULL
2021-07-12 17:46:16.384  INFO main sc_cli::runner: 💾 Database: RocksDb at /tmp/substrateKm2Dx8/chains/moonbase_alpha/db
2021-07-12 17:46:16.384  INFO main sc_cli::runner: ⛓  Native runtime: moonbase-155 (moonbase-0.tx2.au3)
2021-07-12 17:46:16.420  INFO main moonbeam_cli::command: Parachain id: Id(1000)
2021-07-12 17:46:16.420  INFO main moonbeam_cli::command: Parachain Account: 5Ec4AhPZk8STuex8Wsi9TwDtJQxKqzPJRCH7348Xtcs9vZLJ
2021-07-12 17:46:16.421  INFO main moonbeam_cli::command: Parachain genesis state: 0x000000000000000000000000000000000000000000000000000000000000000000b505bc9a20d69f14620b2417b6d777c398ceb3e32119b9a53507111d1880927c03170a2e7597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400
2021-07-12 17:46:16.532 TRACE main state-db: [🌗] StateDb settings: Constrained(Constraints { max_blocks: Some(256), max_mem: None }). Ref-counting: true
2021-07-12 17:46:16.532 TRACE main state-db: [🌗] DB pruning mode: None
2021-07-12 17:46:16.533 TRACE main state-db: [🌗] Reading pruning journal. Pending #0
2021-07-12 17:46:16.553  INFO main sc_service::client::client: [🌗] 🔨 Initializing Genesis block/state (state: 0xb505…927c, header-hash: 0x91bc…9527)
2021-07-12 17:46:16.554 TRACE main state-db: [🌗] Inserted uncanonicalized changeset 0.0 (75 inserted, 0 deleted)
2021-07-12 17:46:16.555 TRACE main state-db: [🌗] Canonicalizing 0x91bc6e169807aaa54802737e1c504b2577d4fafedd5a02c10293b1cd60e39527
2021-07-12 17:46:16.555 TRACE main state-db: [🌗] Discarding 1 records

[gdzien-co]

I will try on the chain that was failing yesterday but I am afraid that the same thing may happen as it did happen with second attempt node - which after waiting some time and restarting went further and fully synchronized the chain.

[gdzien-co]

The way I tried to start the node does not seem to take the provided arguments:
docker logs -f $(docker run -d --network="host" -v "/data:/data" -u $(id -u ${USER}):$(id -g ${USER}) purestake/moonbeam:v0.9.1 --base-path=/data --chain alphanet --name="GDZIEN-C1-Test2-Temp" --execution wasm --wasm-execution compiled --pruning archive --state-cache-size 1 -- --pruning archive --name="GDZIEN-C1-Test2-Temp (Embedded Relay)" -l state-db=trace,sync=trace)

How else I may try to set those debugging/tracing options?

[crystalin]

@gdzien-co you should try to put the flags before the -- one
-- is used to separate the parameter of the parachain (before) and the relaychain (after)

[gdzien-co]

Perfect, log is now way faster to scroll the screen, if the node will fail (I am running it as the 2nd one on the same network, so some network port collision is expected).

[gdzien-co]

log-new-net.zip
This file deflates to 109MiB. Contains error with debugging options.

Can provide corrupted files upon request.

[crystalin]

Closing it in favor of #541