[Parachain Onboarding | Slot Request] BiFrost - ParaId: 2030 #59
Assignees
Labels
blocked
core
Support task to be completed by Paseo Core team
onboard-para
Onboard a new parachain to Paseo
Q3 - 2024
3rd Quarter of Paseo Testnet Project
RocMigration
Migration request from Rococo
Milestone
Comments
|
@hbulgarini @al3mart @educlerici-zondax Hello， 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 |
In addition, could you please search in your raw chain spec if this key is present? that is the key for |
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 @al3mart Maybe I need to replace the new paseo version bifrost , but when I replace the relay chain parameters, the bifrost will be error: the command is: And the bifrost-rococo didn't error, and the command is: |
|
|
Thanks, everyone. I have resolved the command problem with paseo-chain-spec file and command now is : 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. |
|
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? |
|
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 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! 👌 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 |
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 |
@hbulgarini I cleaned up the db file and restarted it as you suggested，and with the debug parameter |
|
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: |
|
i can spot this at the very begining:
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
changed the title
|
@educlerici-zondax 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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: