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

Westend People chain - not discovering peers #3856

Open
2 tasks done
miloskriz opened this issue Mar 27, 2024 · 2 comments
Open
2 tasks done

Westend People chain - not discovering peers #3856

miloskriz opened this issue Mar 27, 2024 · 2 comments
Labels
I2-bug The node fails to follow expected behavior. I10-unconfirmed Issue might be valid, but it's not yet known.

Comments

@miloskriz
Copy link
Contributor

Is there an existing issue?

  • I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

  • This is not a support question.

Description of bug

Dear team, hello,

New nodes trying to connect to the People system chain in Westend are not discovering any peers. We are led to believe this is as a consequence of an error in the current chainspecs available in this repository.

Please find the logs of a node trying to connect to this chain here, the command used for this node is shown further below. An interesting point to highlight from the logs is that the genesis block look different than the one shown in the polkajs explorer:

[Parachain] 🔨 Initializing Genesis block/state (state: 0x2bcb…3f58, header-hash: 0x5bc9…7d9a)

Finally, please note that the following bootnodes of the specification file are not responding to ping or telnet requests on the relevant ports (30333 & 443):

  • westend-people-collator-node-2.parity-testnet.parity.io
  • westend-people-collator-node-3.parity-testnet.parity.io

regarding the rest of the bootnodes, we cannot comment on whether their peerIds are still correct for the relevant chain.

We would be grateful if prior to updating the whole chainspecs you could kindly advise the details of at least one current bootnode to try connect?

Many thanks!

Best regards

Milos

Steps to reproduce

using the latest polkadot-parachain binary (v1.9.0), execute it as:

polkadot-parachain \
  --name TEST_WND_PEOPLE \
  --chain people-westend \
  --database paritydb \
  --state-pruning 256 \
  --log sync=warn,afg=warn,babe=warn \
  --no-mdns \
  --no-hardware-benchmarks \
  --rpc-external \
  --prometheus-external \
  --rpc-methods safe \
  --rpc-cors all 
@miloskriz miloskriz added I10-unconfirmed Issue might be valid, but it's not yet known. I2-bug The node fails to follow expected behavior. labels Mar 27, 2024
@miloskriz
Copy link
Contributor Author

Dear team,

Found it!!!.. the correct chainspecs are still not merged to main.

This issue can now be closed!

Cheers!

Milos

@miloskriz
Copy link
Contributor Author

Dear team, dear @NachoPal, hello,

Just reopening this issue to remind that the correct chainspecs for people-westend still need to be merged into the master branch.

The current chainspecs of this chain are still stored in this commit that belongs to this branch and is part of pull request #2931.

The Infrastructure Builders' Programme has also championed the alternative pull request #3957 inserting all bootnodes provided to the chain by the programme..

Please consider merging them at your earliest convenience?

Many thanks!

Milos

@miloskriz miloskriz reopened this Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I2-bug The node fails to follow expected behavior. I10-unconfirmed Issue might be valid, but it's not yet known.
Projects
None yet
Development

No branches or pull requests

1 participant