Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parachain nodes are not peering with default config #171

Closed
brunopgalvao opened this issue Mar 3, 2022 · 6 comments
Closed

Parachain nodes are not peering with default config #171

brunopgalvao opened this issue Mar 3, 2022 · 6 comments
Assignees

Comments

@brunopgalvao
Copy link
Contributor

brunopgalvao commented Mar 3, 2022

Using the default config with an additional parachain node, the relay-chain node and the parachain nodes are up and running but the parachain nodes are not peering. If I add the --force-authoring flag to the parachain nodes, the parachain starts creating blocks.

@brunopgalvao
Copy link
Contributor Author

brunopgalvao commented Mar 3, 2022

Is --force-authoring required, according to these docs it is:

And according to these it is not:

If anyone can shed some light on this that would be great.

@dharjeezy
Copy link

I am really experiencing this same issue.

@brunopgalvao brunopgalvao self-assigned this Mar 4, 2022
@al3mart
Copy link
Contributor

al3mart commented Mar 4, 2022

polkadot-launch itself will add the flag --force-authoring when we are running one node alone for the parachain. See source here

A pair of things to check here then:

  • Nodes are connected. We can run as many nodes as we want but if they are not properly connected, they will not produce.
  • Check the paraId in the state of our para is matching the paraId where the wasm and state of the para has been registered on the relay chain. As mention here

If the configuration doesn't deviates much from a default config these should be one of the few checks to make for the parachain working as expected. For more custom chain specs and set ups the possible points of failure may vary

@brunopgalvao
Copy link
Contributor Author

brunopgalvao commented Mar 7, 2022

For parachain node peering to work for me, I had to replace the id field in the config.json:

"id": "200",

with the chain key and value of the parachain I am launching like this:

"chain": "statemine-dev",

then my parachain nodes peer, otherwise they do not.

Here is my config for reference:

@brunopgalvao brunopgalvao changed the title Parachain nodes not creating blocks with default config Parachain nodes are not peering with default config Mar 7, 2022
@dharjeezy
Copy link

For parachain node peering to work for me, I had to replace the id field in the config.json:

"id": "200",

with the chain field like this:

"chain": "statemine-dev",

then my parachain nodes peer, otherwise they do not.

Here is my config for reference:

Alright... Thanks so much, will try this out and give you feedback.

@brunopgalvao
Copy link
Contributor Author

Closing this as it has resolved the stated issue. @dharjeezy if you are still having issues with running yours I would recommend opening a small replicable concise question on substrate.stackexchange.com as polkadot-launch does seem to be peering parachain nodes fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants