Closed TomatoAres closed 2 months ago
@hbulgarini @al3mart @educlerici-zondax Hello, I want to migrate bifrost from rococo to paseo,
I have read this migration doc and our I have the bifrost binary
What do I need to do next?
@hbulgarini @al3mart @educlerici-zondax Hello, I want to migrate bifrost from rococo to paseo,
I have read this migration doc and our I have the bifrost binary
What do I need to do next?
Hello! We will onboard the parachain this week, are the collators up and running already?
@hbulgarini @al3mart @educlerici-zondax Hello, I want to migrate bifrost from rococo to paseo, I have read this migration doc and our I have the bifrost binary What do I need to do next?
Hello! We will onboard the parachain this week, are the collators up and running already?
Yes, the rococo-bifrost is running
hey @TomatoAres , the parachain was onboarded but the block production is stalled. Any errors in the logs? Have you changed the protocol id from the chain spec?
Hi @TomatoAres it would be great if you could share the logs of your collators
hey @TomatoAres , the parachain was onboarded but the block production is stalled. Any errors in the logs? Have you changed the protocol id from the chain spec?
In addition, could you please search in your raw chain spec if this key is present?
0x45323df7cc47150b3930e2666b0aa313a2bca190d36bd834cc73a38fc213ecbd
that is the key for parachainSystem.lastRelayChainBlockNumber
value that holds the last relay chain block number. If you are migrating from Rococo an that value is present on the chain spec, then it will not work.
To solve it, you must remove the key and generate the wasm and state again so we can update it.
hey @TomatoAres , the parachain was onboarded but the block production is stalled. Any errors in the logs? Have you changed the protocol id from the chain spec?
hello @hbulgarini ,the parachain(bifrost-rococo) produce block slowly in the past recent weeks,and no error in the logs
The protocol id is same in bifrost-rococo and bifrost-paseo, is
"protocolId": "bifrost"
@al3mart Maybe I need to replace the new paseo version bifrost , but when I replace the relay chain parameters, the bifrost will be error:
2024-05-16 16:43:13 Bifrost Collator
2024-05-16 16:43:13 ✌️ version 0.9.98-4b2f8b80e99
2024-05-16 16:43:13 ❤️ by Liebi Technologies <bifrost@liebi.com>, 2019-2024
2024-05-16 16:43:13 📋 Chain specification: Bifrost Paseo
2024-05-16 16:43:13 🏷 Node name: bifrost-paseo-eu1
2024-05-16 16:43:13 👤 Role: AUTHORITY
2024-05-16 16:43:13 💾 Database: RocksDb at node/chains/bifrost-paseo/db/full
Error: Input("Relay chain argument error: Invalid input: Error opening spec file `paseo`: No such file or directory (os error 2)")
the command is:
bifrost --name bifrost-paseo-eu1 \
--base-path node \
--keystore-path node/keystore \
--chain bifrost-paseo \
--force-authoring \
--collator \
--unsafe-rpc-external \
--rpc-methods=unsafe \
--rpc-max-connections 10000 \
--rpc-cors all \
--prometheus-external \
--wasm-execution compiled \
--listen-addr /ip4/0.0.0.0/tcp/30333 \
-- \
--chain paseo
And the bifrost-rococo didn't error, and the command is:
bifrost --name bifrost-paseo-eu1 \
--base-path node \
--keystore-path node/keystore \
--chain bifrost-kusama-rococo \
--force-authoring \
--collator \
--unsafe-rpc-external \
--rpc-methods=unsafe \
--rpc-max-connections 10000 \
--rpc-cors all \
--prometheus-external \
--wasm-execution compiled \
--listen-addr /ip4/0.0.0.0/tcp/30333 \
-- \
--chain rococo
0x45323df7cc47150b3930e2666b0aa313a2bca190d36bd834cc73a38fc213ecbd @hbulgarini I can't find the
0x45323df7cc47150b3930e2666b0aa313a2bca190d36bd834cc73a38fc213ecbd
in
parachainSystem.lastRelayChainBlockNumber
is 10,034,394
:
Thanks, everyone.
I have resolved the command problem with paseo-chain-spec file
and command now is :
bifrost --name bifrost-paseo-eu1 \
--base-path node \
--keystore-path node/keystore \
--chain bifrost-paseo \
--force-authoring \
--collator \
--unsafe-rpc-external \
--rpc-methods=unsafe \
--rpc-max-connections 10000 \
--rpc-cors all \
--prometheus-external \
--wasm-execution compiled \
--listen-addr /ip4/0.0.0.0/tcp/30333 \
-- \
--chain paseo.raw.json
The relay chain has started to synchronize, and it will probably take some time for the parallel chain to start producing blocks. Currently, there is an error with the parallel chain in the log, and I'm not sure if it will affect the operation.
3|eu1 | 2024-05-16 17:03:59 [Relaychain] ⚙️ Syncing 140.6 bps, target=#1234784 (8 peers), best: #67968 (0x9670…0f46), finalized #67584 (0xdd05…bac1), ⬇ 658.8kiB/s ⬆ 0.9kiB/s
3|eu1 | 2024-05-16 17:03:59 [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.1kiB/s ⬆ 0.1kiB/s
3|eu1 | 2024-05-16 17:03:59 [Parachain🌈] Report 12D3KooWCUKdehGqnTpL8MyvbYcuqpnZP43N5Dhw5zypKSUToojA: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting.
Nothing alarming for now, let's wait for it to end syncing
Thank you !
Syncing has been completed and the parachain is now generating blocks.
Bifrost log has a error like this, do you have some suggestions?
0|eu1 | 2024-05-16 23:33:30 [Parachain🌈] err=Error { inner: Proposing
0|eu1 | Caused by:
0|eu1 | 0: Error at calling runtime api: Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed
0|eu1 | WASM backtrace:
0|eu1 | error while executing at wasm backtrace:
0|eu1 | 0: 0x72a3d3 - <unknown>!rust_begin_unwind
0|eu1 | 1: 0x6bdaf3 - <unknown>!core::panicking::panic_fmt::ha38e6eecb0b0460a
0|eu1 | 2: 0x6253cb - <unknown>!<pallet_aura::pallet::Pallet<T> as frame_support::traits::hooks::OnInitialize<<<<T as frame_system::pallet::Config>::Block as sp_runtime::traits::HeaderProvider>::HeaderT as sp_runtime::traits::Header>::Number>>::on_initialize::h151035c1b15da394
0|eu1 | 3: 0x1089a8 - <unknown>!<(TupleElement0,TupleElement1,TupleElement2,TupleElement3,TupleElement4,TupleElement5,TupleElement6,TupleElement7,TupleElement8,TupleElement9,TupleElement10,TupleElement11,TupleElement12,TupleElement13,TupleElement14,TupleElement15,TupleElement16,TupleElement17,TupleElement18,TupleElement19,TupleElement20,TupleElement21,TupleElement22,TupleElement23,TupleElement24,TupleElement25,TupleElement26,TupleElement27,TupleElement28,TupleElement29,TupleElement30,TupleElement31,TupleElement32,TupleElement33,TupleElement34,TupleElement35,TupleElement36,TupleElement37,TupleElement38,TupleElement39,TupleElement40,TupleElement41,TupleElement42,TupleElement43,TupleElement44,TupleElement45,TupleElement46,TupleElement47,TupleElement48,TupleElement49,TupleElement50,TupleElement51,TupleElement52,TupleElement53,TupleElement54,TupleElement55,TupleElement56,TupleElement57,TupleElement58,TupleElement59,TupleElement60,TupleElement61,TupleElement62,TupleElement63,TupleElement64,TupleElement65,TupleElement66,TupleElement67,TupleElement68,TupleElement69,TupleElement70,TupleElement71) as frame_support::traits::hooks::OnInitialize<BlockNumber>>::on_initialize::hf3df462b30d801a0
0|eu1 | 4: 0x243baf - <unknown>!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::initialize_block::h9b2c2cba631acaba
0|eu1 | 5: 0x496601 - <unknown>!Core_initialize_block
0|eu1 | 1: Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed
0|eu1 | WASM backtrace:
0|eu1 | error while executing at wasm backtrace:
0|eu1 | 0: 0x72a3d3 - <unknown>!rust_begin_unwind
0|eu1 | 1: 0x6bdaf3 - <unknown>!core::panicking::panic_fmt::ha38e6eecb0b0460a
0|eu1 | 2: 0x6253cb - <unknown>!<pallet_aura::pallet::Pallet<T> as frame_support::traits::hooks::OnInitialize<<<<T as frame_system::pallet::Config>::Block as sp_runtime::traits::HeaderProvider>::HeaderT as sp_runtime::traits::Header>::Number>>::on_initialize::h151035c1b15da394
0|eu1 | 3: 0x1089a8 - <unknown>!<(TupleElement0,TupleElement1,TupleElement2,TupleElement3,TupleElement4,TupleElement5,TupleElement6,TupleElement7,TupleElement8,TupleElement9,TupleElement10,TupleElement11,TupleElement12,TupleElement13,TupleElement14,TupleElement15,TupleElement16,TupleElement17,TupleElement18,TupleElement19,TupleElement20,TupleElement21,TupleElement22,TupleElement23,TupleElement24,TupleElement25,TupleElement26,TupleElement27,TupleElement28,TupleElement29,TupleElement30,TupleElement31,TupleElement32,TupleElement33,TupleElement34,TupleElement35,TupleElement36,TupleElement37,TupleElement38,TupleElement39,TupleElement40,TupleElement41,TupleElement42,TupleElement43,TupleElement44,TupleElement45,TupleElement46,TupleElement47,TupleElement48,TupleElement49,TupleElement50,TupleElement51,TupleElement52,TupleElement53,TupleElement54,TupleElement55,TupleElement56,TupleElement57,TupleElement58,TupleElement59,TupleElement60,TupleElement61,TupleElement62,TupleElement63,TupleElement64,TupleElement65,TupleElement66,TupleElement67,TupleElement68,TupleElement69,TupleElement70,TupleElement71) as frame_support::traits::hooks::OnInitialize<BlockNumber>>::on_initialize::hf3df462b30d801a0
0|eu1 | 4: 0x243baf - <unknown>!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::initialize_block::h9b2c2cba631acaba
0|eu1 | 5: 0x496601 - <unknown>!Core_initialize_block }
0|eu1 | 2024-05-16 23:33:30 [Relaychain] ✨ Imported #1238680 (0x3523…ad8f)
0|eu1 | 2024-05-16 23:33:30 [Parachain🌈] 🙌 Starting consensus session on top of parent 0x19b60750923ef2510d0897a48223e9f7e2180ca2e32e044a8f68e7320ad4ebd5
Can't put my finger on a concrete issue just with those logs.
I'd like to know what version of polkadot are you depending on right now. The problem might come from async backing related stuff.
Some of the last problems / solutions observed in regards to async backing have been:
Hey guys, bifrost-paseo parachain transitioned to parathread and not produced blocks for server hours.
There seems to be no visibility of the slot lease on Paseo, which I believe is instrumental to the proper functioning and performance of the Bifrost Paseo. The unavailability of the slot lease and the halt in block production have raised concerns about the stability and reliability of the chain.
I would greatly appreciate it if you could investigate this matter and provide more insight regarding this issue. I'm particularly interested in understanding why this transition happened and what can be done to resolve it.
slots assigned! :ok_hand:
And manager lock removed.
@TomatoAres I'm curious about if you could figure out what was causing those panics in your runtime.
Hey @TomatoAres! is the runtime still trowing panics?
No, there no panics in log, but it can't generate blocks now
No, there no panics in log, but it can't generate blocks now
If you don't have a state, could you please prune the DB and restart the collators?
@TomatoAres could you also share the logs of your collator run with -lbasic-authorship=debug
?
No, there no panics in log, but it can't generate blocks now
If you don't have a state, could you please prune the DB and restart the collators?
@hbulgarini I cleaned up the db file and restarted it as you suggested,and with the debug parameter -lbasic-authorship=debug
@al3mart
Can you share the logs, please :)
@TomatoAres just a friendly reminder if you can share the logs please 🙏
@educlerici-zondax @al3mart There is no error in logs, and the log file is 151M, too large to upload
I paste some log here:
head -n 200 paseo.log
2024-06-07 18:27:00.288 INFO main sc_cli::runner: Bifrost Collator
2024-06-07 18:27:00.288 INFO main sc_cli::runner: ✌️ version 0.9.98-4b2f8b80e99
2024-06-07 18:27:00.288 INFO main sc_cli::runner: ❤️ by Liebi Technologies <bifrost@liebi.com>, 2019-2024
2024-06-07 18:27:00.288 INFO main sc_cli::runner: 📋 Chain specification: Bifrost Paseo
2024-06-07 18:27:00.288 INFO main sc_cli::runner: 🏷 Node name: bifrost-paseo-eu1
2024-06-07 18:27:00.288 INFO main sc_cli::runner: 👤 Role: AUTHORITY
2024-06-07 18:27:00.288 INFO main sc_cli::runner: 💾 Database: RocksDb at node/chains/bifrost-paseo/db/full
2024-06-07 18:27:02.976 INFO main bifrost_cli::command: Parachain id: Id(2030)
2024-06-07 18:27:02.976 INFO main bifrost_cli::command: Parachain Account: 5Ec4AhPax3JR2qp8L9F1NiC8yjQcQAK1JmU5Nyyu3MXHPCmc
2024-06-07 18:27:02.976 INFO main bifrost_cli::command: Is collating: yes
2024-06-07 18:27:03.053 ERROR main bifrost_parachain_staking::pallet: [Parachain🌈] 💥 keeping old session because of empty collator set!
2024-06-07 18:27:03.053 ERROR main bifrost_parachain_staking::pallet: [Parachain🌈] 💥 keeping old session because of empty collator set!
2024-06-07 18:27:12.533 INFO main sub-libp2p: [Relaychain] 🏷 Local node identity is: 12D3KooWJEv14i5Zwsxexr6gfcpR8ydCd3RRxfEAnLh1H7rq3u96
2024-06-07 18:27:12.605 INFO main sc_sysinfo: [Relaychain] 💻 Operating system: linux
2024-06-07 18:27:12.605 INFO main sc_sysinfo: [Relaychain] 💻 CPU architecture: x86_64
2024-06-07 18:27:12.605 INFO main sc_sysinfo: [Relaychain] 💻 Target environment: gnu
2024-06-07 18:27:12.605 INFO main sc_sysinfo: [Relaychain] 💻 CPU: Intel(R) Xeon(R) Platinum 8255C CPU @ 2.50GHz
2024-06-07 18:27:12.605 INFO main sc_sysinfo: [Relaychain] 💻 CPU cores: 4
2024-06-07 18:27:12.605 INFO main sc_sysinfo: [Relaychain] 💻 Memory: 7425MB
2024-06-07 18:27:12.605 INFO main sc_sysinfo: [Relaychain] 💻 Kernel: 5.15.0-86-generic
2024-06-07 18:27:12.605 INFO main sc_sysinfo: [Relaychain] 💻 Linux distribution: Ubuntu 22.04 LTS
2024-06-07 18:27:12.605 INFO main sc_sysinfo: [Relaychain] 💻 Virtual machine: yes
2024-06-07 18:27:12.605 INFO main sc_service::builder: [Relaychain] 📦 Highest known block at #1549303
2024-06-07 18:27:12.605 INFO tokio-runtime-worker substrate_prometheus_endpoint: [Relaychain] 〽️ Prometheus exporter started at 127.0.0.1:9616
2024-06-07 18:27:12.606 INFO main sc_rpc_server: [Relaychain] Running JSON-RPC server: addr=127.0.0.1:9944, allowed origins=["http://localhost:*", "http://127.0.0.1:*", "https://localhost:*", "https://127.0.0.1:*", "https://polkadot.js.org"]
2024-06-07 18:27:12.606 INFO main sc_sysinfo: [Relaychain] 🏁 CPU score: 991.03 MiBs
2024-06-07 18:27:12.606 INFO main sc_sysinfo: [Relaychain] 🏁 Memory score: 4.62 GiBs
2024-06-07 18:27:12.606 INFO main sc_sysinfo: [Relaychain] 🏁 Disk score (seq. writes): 322.32 MiBs
2024-06-07 18:27:12.606 INFO main sc_sysinfo: [Relaychain] 🏁 Disk score (rand. writes): 75.15 MiBs
2024-06-07 18:27:12.613 INFO main sub-libp2p: [Parachain🌈] 🏷 Local node identity is: 12D3KooWFZHpXfK7XKJQEPgvhkC3SzDTJCVHzSp54LYGtYUmvg82
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 💻 Operating system: linux
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 💻 CPU architecture: x86_64
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 💻 Target environment: gnu
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 💻 CPU: Intel(R) Xeon(R) Platinum 8255C CPU @ 2.50GHz
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 💻 CPU cores: 4
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 💻 Memory: 7425MB
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 💻 Kernel: 5.15.0-86-generic
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 💻 Linux distribution: Ubuntu 22.04 LTS
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 💻 Virtual machine: yes
2024-06-07 18:27:12.619 INFO main sc_service::builder: [Parachain🌈] 📦 Highest known block at #0
2024-06-07 18:27:12.619 INFO main sc_rpc_server: [Parachain🌈] Running JSON-RPC server: addr=0.0.0.0:36453, allowed origins=["*"]
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 🏁 CPU score: 991.03 MiBs
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 🏁 Memory score: 4.62 GiBs
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 🏁 Disk score (seq. writes): 322.32 MiBs
2024-06-07 18:27:12.619 INFO main sc_sysinfo: [Parachain🌈] 🏁 Disk score (rand. writes): 75.15 MiBs
2024-06-07 18:27:12.619 INFO tokio-runtime-worker substrate_prometheus_endpoint: [Parachain🌈] 〽️ Prometheus exporter started at 0.0.0.0:9615
2024-06-07 18:27:12.621 INFO tokio-runtime-worker libp2p_mdns::behaviour: [Parachain🌈] discovered: 12D3KooWJEv14i5Zwsxexr6gfcpR8ydCd3RRxfEAnLh1H7rq3u96 /ip4/172.28.16.17/tcp/30334/ws
2024-06-07 18:27:12.621 INFO tokio-runtime-worker libp2p_mdns::behaviour: [Relaychain] discovered: 12D3KooWFZHpXfK7XKJQEPgvhkC3SzDTJCVHzSp54LYGtYUmvg82 /ip4/172.28.16.17/tcp/30333
2024-06-07 18:27:13.254 INFO tokio-runtime-worker sub-libp2p: [Relaychain] 🔍 Discovered new external address for our node: /ip4/162.62.216.251/tcp/30334/ws/p2p/12D3KooWJEv14i5Zwsxexr6gfcpR8ydCd3RRxfEAnLh1H7rq3u96
2024-06-07 18:27:14.710 INFO tokio-runtime-worker sub-libp2p: [Parachain🌈] 🔍 Discovered new external address for our node: /dns4/eu.bifrost-rococo.liebi.com/tcp/30333/p2p/12D3KooWFZHpXfK7XKJQEPgvhkC3SzDTJCVHzSp54LYGtYUmvg82
2024-06-07 18:27:17.497 WARN tokio-runtime-worker parachain::availability-store: [Relaychain] Candidate included without being backed? candidate_hash=0xe7770189b751c35bc60d907d0c4f77b41499947d0c21e292c434a86143634539 traceID=307669581545883681577543258739840087988
2024-06-07 18:27:17.497 WARN tokio-runtime-worker parachain::availability-store: [Relaychain] Candidate included without being backed? candidate_hash=0x89f13b2ffda625dc040cbebddc576ff3fd36ded6e5f4f57c49417454162fc875 traceID=183356779429831189622268007680012939251
2024-06-07 18:27:17.606 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (7 peers), best: #1549326 (0xae11…0d0c), finalized #1549324 (0x25db…7dd6), ⬇ 142.0kiB/s ⬆ 37.9kiB/s
2024-06-07 18:27:17.620 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.4kiB/s ⬆ 0.4kiB/s
2024-06-07 18:27:18.078 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549327 (0x97ab…b40b)
2024-06-07 18:27:18.427 INFO tokio-runtime-worker sc_informant: [Relaychain] ♻️ Reorg on #1549327,0x97ab…b40b to #1549327,0xff7e…53d5, common ancestor #1549326,0xae11…0d0c
2024-06-07 18:27:18.427 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549327 (0xff7e…53d5)
2024-06-07 18:27:22.607 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (8 peers), best: #1549327 (0xff7e…53d5), finalized #1549324 (0x25db…7dd6), ⬇ 69.1kiB/s ⬆ 41.9kiB/s
2024-06-07 18:27:22.620 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 70 B/s ⬆ 26 B/s
2024-06-07 18:27:24.286 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549328 (0xc05f…abc4)
2024-06-07 18:27:27.607 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (7 peers), best: #1549328 (0xc05f…abc4), finalized #1549325 (0xe61d…2c06), ⬇ 93.5kiB/s ⬆ 46.6kiB/s
2024-06-07 18:27:27.621 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.2kiB/s ⬆ 0.2kiB/s
2024-06-07 18:27:30.084 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549329 (0x2a70…87df)
2024-06-07 18:27:30.100 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549329 (0x1237…c39b)
2024-06-07 18:27:30.118 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549329 (0xe092…c99b)
2024-06-07 18:27:32.607 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (9 peers), best: #1549329 (0x2a70…87df), finalized #1549326 (0xae11…0d0c), ⬇ 20.2kiB/s ⬆ 43.5kiB/s
2024-06-07 18:27:32.621 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 83 B/s ⬆ 39 B/s
2024-06-07 18:27:32.621 WARN tokio-runtime-worker telemetry: [Parachain🌈] ❌ Error while dialing /dns/telemetry.polkadot.io/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Timeout }
2024-06-07 18:27:36.184 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549330 (0x7991…5531)
2024-06-07 18:27:37.607 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (10 peers), best: #1549330 (0x7991…5531), finalized #1549327 (0xff7e…53d5), ⬇ 32.3kiB/s ⬆ 27.3kiB/s
2024-06-07 18:27:37.621 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.2kiB/s ⬆ 0.2kiB/s
2024-06-07 18:27:42.076 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549331 (0xc9b5…037b)
2024-06-07 18:27:42.608 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549331 (0xc9b5…037b), finalized #1549328 (0xc05f…abc4), ⬇ 19.7kiB/s ⬆ 47.2kiB/s
2024-06-07 18:27:42.621 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0 ⬆ 0
2024-06-07 18:27:47.608 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549331 (0xc9b5…037b), finalized #1549329 (0x2a70…87df), ⬇ 70.0kiB/s ⬆ 29.7kiB/s
2024-06-07 18:27:47.622 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.2kiB/s ⬆ 0.2kiB/s
2024-06-07 18:27:48.407 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549332 (0xe0c8…07e4)
2024-06-07 18:27:52.608 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549332 (0xe0c8…07e4), finalized #1549329 (0x2a70…87df), ⬇ 25.1kiB/s ⬆ 25.6kiB/s
2024-06-07 18:27:52.622 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 21 B/s ⬆ 14 B/s
2024-06-07 18:27:54.339 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549333 (0xbef7…135b)
2024-06-07 18:27:57.609 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549333 (0xbef7…135b), finalized #1549330 (0x7991…5531), ⬇ 18.0kiB/s ⬆ 34.3kiB/s
2024-06-07 18:27:57.622 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 21 B/s ⬆ 21 B/s
2024-06-07 18:28:00.080 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549334 (0x3590…c1d3)
2024-06-07 18:28:02.609 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549334 (0x3590…c1d3), finalized #1549331 (0xc9b5…037b), ⬇ 8.8kiB/s ⬆ 23.9kiB/s
2024-06-07 18:28:02.622 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.1kiB/s ⬆ 0.2kiB/s
2024-06-07 18:28:06.083 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549335 (0x9ff3…2834)
2024-06-07 18:28:07.609 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549335 (0x9ff3…2834), finalized #1549332 (0xe0c8…07e4), ⬇ 12.5kiB/s ⬆ 32.7kiB/s
2024-06-07 18:28:07.623 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0 ⬆ 0
2024-06-07 18:28:12.111 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549336 (0x58b0…ce60)
2024-06-07 18:28:12.609 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549336 (0x58b0…ce60), finalized #1549333 (0xbef7…135b), ⬇ 4.9kiB/s ⬆ 22.9kiB/s
2024-06-07 18:28:12.623 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.1kiB/s ⬆ 0.1kiB/s
2024-06-07 18:28:17.610 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549336 (0x58b0…ce60), finalized #1549333 (0xbef7…135b), ⬇ 72.3kiB/s ⬆ 46.1kiB/s
2024-06-07 18:28:17.623 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 83 B/s ⬆ 39 B/s
2024-06-07 18:28:18.127 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549337 (0x50fb…c892)
2024-06-07 18:28:18.963 INFO tokio-runtime-worker sc_informant: [Relaychain] ♻️ Reorg on #1549337,0x50fb…c892 to #1549337,0xf487…a281, common ancestor #1549336,0x58b0…ce60
2024-06-07 18:28:18.963 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549337 (0xf487…a281)
2024-06-07 18:28:22.610 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549337 (0xf487…a281), finalized #1549335 (0x9ff3…2834), ⬇ 38.0kiB/s ⬆ 59.7kiB/s
2024-06-07 18:28:22.623 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.1kiB/s ⬆ 0.2kiB/s
2024-06-07 18:28:24.078 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549338 (0x906b…f21c)
2024-06-07 18:28:24.096 INFO tokio-runtime-worker sc_informant: [Relaychain] ♻️ Reorg on #1549338,0x906b…f21c to #1549338,0xd258…ebd1, common ancestor #1549337,0xf487…a281
2024-06-07 18:28:24.096 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549338 (0xd258…ebd1)
2024-06-07 18:28:26.688 WARN tokio-runtime-worker peerset: [Relaychain] Report 12D3KooWBsBE29CTQ4y7bF6G8stugjZfAQibgZdKTiaZzBB5Eqv1: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting.
2024-06-07 18:28:27.610 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549338 (0xd258…ebd1), finalized #1549335 (0x9ff3…2834), ⬇ 20.9kiB/s ⬆ 47.9kiB/s
2024-06-07 18:28:27.624 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0 ⬆ 0
2024-06-07 18:28:30.073 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549339 (0xd3d6…0f8f)
2024-06-07 18:28:30.090 INFO tokio-runtime-worker sc_informant: [Relaychain] ♻️ Reorg on #1549339,0xd3d6…0f8f to #1549339,0x3bdb…d90f, common ancestor #1549338,0xd258…ebd1
2024-06-07 18:28:30.090 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549339 (0x3bdb…d90f)
2024-06-07 18:28:30.279 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549339 (0xff0d…0a2a)
2024-06-07 18:28:30.356 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549339 (0xc533…a394)
2024-06-07 18:28:32.611 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549339 (0x3bdb…d90f), finalized #1549336 (0x58b0…ce60), ⬇ 30.7kiB/s ⬆ 72.6kiB/s
2024-06-07 18:28:32.624 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.2kiB/s ⬆ 0.2kiB/s
2024-06-07 18:28:36.274 INFO tokio-runtime-worker sc_informant: [Relaychain] ♻️ Reorg on #1549339,0x3bdb…d90f to #1549340,0x3551…d3f8, common ancestor #1549338,0xd258…ebd1
2024-06-07 18:28:36.274 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549340 (0x3551…d3f8)
2024-06-07 18:28:37.611 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549340 (0x3551…d3f8), finalized #1549337 (0xf487…a281), ⬇ 16.5kiB/s ⬆ 31.3kiB/s
2024-06-07 18:28:37.624 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 26 B/s ⬆ 19 B/s
2024-06-07 18:28:42.348 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549341 (0x6670…440c)
2024-06-07 18:28:42.611 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549341 (0x6670…440c), finalized #1549338 (0xd258…ebd1), ⬇ 16.8kiB/s ⬆ 31.7kiB/s
2024-06-07 18:28:42.624 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.1kiB/s ⬆ 0.2kiB/s
2024-06-07 18:28:47.611 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549341 (0x6670…440c), finalized #1549339 (0xff0d…0a2a), ⬇ 18.1kiB/s ⬆ 35.6kiB/s
2024-06-07 18:28:47.625 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 33 B/s ⬆ 26 B/s
2024-06-07 18:28:48.070 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549342 (0x2ed7…2e71)
2024-06-07 18:28:52.612 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549342 (0x2ed7…2e71), finalized #1549339 (0xff0d…0a2a), ⬇ 17.9kiB/s ⬆ 24.5kiB/s
2024-06-07 18:28:52.625 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 42 B/s ⬆ 56 B/s
2024-06-07 18:28:54.282 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549343 (0x2832…99cc)
2024-06-07 18:28:57.612 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549343 (0x2832…99cc), finalized #1549340 (0x3551…d3f8), ⬇ 14.8kiB/s ⬆ 33.9kiB/s
2024-06-07 18:28:57.625 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.1kiB/s ⬆ 0.1kiB/s
2024-06-07 18:29:00.282 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549344 (0x1586…5877)
2024-06-07 18:29:02.612 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549344 (0x1586…5877), finalized #1549341 (0x6670…440c), ⬇ 18.3kiB/s ⬆ 33.5kiB/s
2024-06-07 18:29:02.625 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 12 B/s ⬆ 12 B/s
2024-06-07 18:29:06.080 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549345 (0xe6a7…1311)
2024-06-07 18:29:07.613 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549345 (0xe6a7…1311), finalized #1549341 (0x6670…440c), ⬇ 5.5kiB/s ⬆ 19.7kiB/s
2024-06-07 18:29:07.626 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.1kiB/s ⬆ 0.2kiB/s
2024-06-07 18:29:12.065 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549346 (0x322d…6c58)
2024-06-07 18:29:12.613 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549346 (0x322d…6c58), finalized #1549343 (0x2832…99cc), ⬇ 19.9kiB/s ⬆ 46.8kiB/s
2024-06-07 18:29:12.626 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0 ⬆ 0
2024-06-07 18:29:17.613 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549346 (0x322d…6c58), finalized #1549344 (0x1586…5877), ⬇ 15.9kiB/s ⬆ 21.9kiB/s
2024-06-07 18:29:17.626 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.2kiB/s ⬆ 0.2kiB/s
2024-06-07 18:29:18.114 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549347 (0x457f…eca0)
2024-06-07 18:29:22.613 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549347 (0x457f…eca0), finalized #1549344 (0x1586…5877), ⬇ 66.7kiB/s ⬆ 60.6kiB/s
2024-06-07 18:29:22.626 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0 ⬆ 0
2024-06-07 18:29:24.058 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549348 (0x824d…4fd5)
2024-06-07 18:29:27.614 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549348 (0x824d…4fd5), finalized #1549345 (0xe6a7…1311), ⬇ 12.4kiB/s ⬆ 29.8kiB/s
2024-06-07 18:29:27.626 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.1kiB/s ⬆ 0.1kiB/s
2024-06-07 18:29:30.145 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549349 (0x553a…5fdc)
2024-06-07 18:29:30.448 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549349 (0x5012…71c0)
2024-06-07 18:29:32.614 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549349 (0x553a…5fdc), finalized #1549346 (0x322d…6c58), ⬇ 33.3kiB/s ⬆ 54.0kiB/s
2024-06-07 18:29:32.627 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 33 B/s ⬆ 47 B/s
2024-06-07 18:29:36.069 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549350 (0x79c0…55a8)
2024-06-07 18:29:36.277 INFO tokio-runtime-worker sc_informant: [Relaychain] ♻️ Reorg on #1549350,0x79c0…55a8 to #1549350,0x57e4…e89f, common ancestor #1549349,0x553a…5fdc
2024-06-07 18:29:36.279 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1549350 (0x57e4…e89f)
2024-06-07 18:29:37.614 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (11 peers), best: #1549350 (0x57e4…e89f), finalized #1549347 (0x457f…eca0), ⬇ 17.8kiB/s ⬆ 26.4kiB/s
2024-06-07 18:29:37.627 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (0 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 26 B/s ⬆ 19 B/s
---skip same logs---
2024-06-24 23:45:48.096 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1789591 (0x906e…d031)
2024-06-24 23:45:48.346 INFO tokio-runtime-worker sc_informant: [Relaychain] ♻️ Reorg on #1789591,0x906e…d031 to #1789591,0x8ad4…f151, common ancestor #1789590,0x9352…d317
2024-06-24 23:45:48.347 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1789591 (0x8ad4…f151)
2024-06-24 23:45:48.995 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (14 peers), best: #1789591 (0x8ad4…f151), finalized #1789588 (0x1a51…1d43), ⬇ 46.5kiB/s ⬆ 88.8kiB/s
2024-06-24 23:45:49.000 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (1 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.2kiB/s ⬆ 0.2kiB/s
2024-06-24 23:45:53.996 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (14 peers), best: #1789591 (0x8ad4…f151), finalized #1789589 (0xd243…a0b6), ⬇ 28.4kiB/s ⬆ 43.8kiB/s
2024-06-24 23:45:54.000 INFO tokio-runtime-worker substrate: [Parachain🌈] 💤 Idle (1 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 12 B/s ⬆ 12 B/s
2024-06-24 23:45:54.181 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1789592 (0xee6c…44e6)
2024-06-24 23:45:58.996 INFO tokio-runtime-worker substrate: [Relaychain] 💤 Idle (14 peers), best: #1789592 (0xee6c…44e6), finalized #1789589 (0xd243…a0b6), ⬇ 132.1kiB/s ⬆ 45.4kiB/s
2024-06-24 23:45:59.000 INFO tokio-runtime-worker substrate: [Parachain🌈] ⚙️ Syncing 0.0 bps, target=#35461 (2 peers), best: #0 (0xec39…4452), finalized #0 (0xec39…4452), ⬇ 0.2kiB/s ⬆ 0.2kiB/s
2024-06-24 23:46:00.092 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1789593 (0x3596…30ca)
2024-06-24 23:46:00.128 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1789593 (0x341c…6a74)
2024-06-24 23:46:00.174 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1789593 (0x7011…221d)
2024-06-24 23:46:00.346 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1789593 (0xfb60…b229)
2024-06-24 23:46:00.844 INFO tokio-runtime-worker substrate: [Relaychain] ✨ Imported #1789593 (0x7076…2b9d)
i can spot this at the very begining:
2024-06-07 18:27:03.053 ERROR main bifrost_parachain_staking::pallet: [Parachain🌈] 💥 keeping old session because of empty collator set!
Is there anything off with session keys?
Also i wonder if this is somehow related:
Hello @TomatoAres, next week we will be doing a cleanup for parachains not producing blocks in paseo. Could you please take a look if the parachain can be fixed so we don't have to offboard it? thanks!
@educlerici-zondax Sorry it's taken so long.
Our code is not very different from bifrost-kusama, and we still haven't found the problem
Can we clean up our 2030 parallel link data again?
Can we re-register the 2030 parallel chain again and started syncing again?
If we re-register the para-chain from 0, Do I need to prune the relay chain data?
parachain is back online after head reset.
Parachain Name
Bifrost Paseo
ParaID
2030
Parachain Manager Account
dDWnEWnx3GUgfugXh9mZtgj4CvJdmd8naYkWYCZGxjfb1Cz
Upload your Genesis State - Do not submit a compressed file.
paseo-genesis.txt
Upload your Validation Code (genesis runtime Wasm) - Do not submit a compressed file.
paseo.wasm.txt